@auto-it/npm
NPM publishing plugin for auto
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @auto-it/npm is a scoped package in the well-established @auto-it namespace (Intuit's auto tool). The Levenshtein match to 'pg' is purely coincidental and not a typosquat. | ai | |
| phantom-deps | phantom-dep:fp-ts | AI (phantom-deps): fp-ts is a legitimate runtime dependency used alongside io-ts in this package; the phantom-dep finding is a false positive for this package. | ai |
Versions (showing 100 of 453)
| Version | Deps | Published |
|---|---|---|
| 10.20.1 | 13 / 5 | |
| 10.20.0 | 13 / 5 | |
| 10.19.0 | 13 / 5 | |
| 10.18.9 | 13 / 5 | |
| 10.18.8 | 13 / 5 | |
| 10.18.7 | 13 / 5 | |
| 10.18.6 | 13 / 5 | |
| 10.18.5 | 13 / 5 | |
| 10.18.4 | 13 / 5 | |
| 10.18.3 | 13 / 5 | |
| 10.18.2 | 13 / 5 | |
| 10.18.1 | 13 / 5 | |
| 10.18.0 | 13 / 5 | |
| 10.17.1 | 13 / 5 | |
| 10.17.0 | 13 / 5 | |
| 10.16.8 | 13 / 5 | |
| 10.16.7 | 13 / 5 | |
| 10.16.6 | 13 / 5 | |
| 10.16.5 | 13 / 5 | |
| 10.16.4 | 13 / 5 | |
| 10.16.3 | 13 / 5 | |
| 10.16.2 | 13 / 5 | |
| 10.16.1 | 13 / 5 | |
| 10.16.0 | 13 / 5 | |
| 10.15.0 | 13 / 5 | |
| 10.14.2 | 13 / 5 | |
| 10.14.1 | 13 / 5 | |
| 10.14.0 | 13 / 5 | |
| 10.13.4 | 13 / 5 | |
| 10.13.3 | 13 / 5 | |
| 10.13.2 | 13 / 5 | |
| 10.13.1 | 13 / 5 | |
| 10.13.0 | 13 / 5 | |
| 10.12.2 | 13 / 5 | |
| 10.12.1 | 13 / 5 | |
| 10.12.0 | 13 / 5 | |
| 10.11.0 | 13 / 5 | |
| 10.10.1 | 13 / 5 | |
| 10.10.0 | 13 / 5 | |
| 10.9.1 | 13 / 5 | |
| 10.9.0 | 13 / 5 | |
| 10.8.0 | 13 / 5 | |
| 10.7.0 | 13 / 5 | |
| 10.6.2 | 13 / 5 | |
| 10.6.1 | 13 / 5 | |
| 10.6.0 | 13 / 5 | |
| 10.5.1 | 13 / 5 | |
| 10.5.0 | 13 / 5 | |
| 10.4.2 | 14 / 6 | |
| 10.4.1 | 14 / 6 | |
| 10.4.0 | 14 / 6 | |
| 10.3.0 | 14 / 6 | |
| 10.2.5 | 14 / 6 | |
| 10.2.4 | 14 / 6 | |
| 10.2.3 | 14 / 6 | |
| 10.2.2 | 14 / 6 | |
| 10.2.1 | 14 / 6 | |
| 10.2.0 | 14 / 6 | |
| 10.1.0 | 14 / 6 | |
| 10.0.2 | 14 / 6 | |
| 10.0.1 | 14 / 6 | |
| 10.0.0 | 14 / 6 | |
| 9.61.0 | 14 / 6 | |
| 9.60.1 | 14 / 6 | |
| 9.60.0 | 14 / 6 | |
| 9.59.1 | 14 / 6 | |
| 9.59.0 | 14 / 6 | |
| 9.58.0 | 14 / 6 | |
| 9.57.0 | 14 / 6 | |
| 9.56.0 | 14 / 6 | |
| 9.55.0 | 14 / 6 | |
| 9.54.6 | 14 / 6 | |
| 9.54.5 | 14 / 6 | |
| 9.54.4 | 14 / 6 | |
| 9.54.3 | 14 / 6 | |
| 9.54.2 | 14 / 6 | |
| 9.54.1 | 14 / 6 | |
| 9.54.0 | 14 / 6 | |
| 9.53.1 | 14 / 6 | |
| 9.53.0 | 14 / 6 | |
| 9.52.0 | 14 / 6 | |
| 9.51.0 | 14 / 6 | |
| 9.50.12 | 14 / 6 | |
| 9.50.11 | 14 / 6 | |
| 9.50.10 | 14 / 6 | |
| 9.50.9 | 14 / 6 | |
| 9.50.8 | 14 / 6 | |
| 9.50.7 | 14 / 6 | |
| 9.50.6 | 14 / 6 | |
| 9.50.5 | 14 / 6 | |
| 9.50.4 | 14 / 6 | |
| 9.50.3 | 14 / 6 | |
| 9.50.2 | 14 / 6 | |
| 9.50.1 | 14 / 6 | |
| 9.50.0 | 14 / 6 | |
| 9.49.6 | 14 / 6 | |
| 9.49.5 | 14 / 6 | |
| 9.49.4 | 14 / 5 | |
| 9.49.3 | 14 / 5 | |
| 9.49.2 | 14 / 5 |
v10.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.