@autosoft/autorepo-api
API for Autorepo.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tsd | AI (phantom-deps): tsd is a dev/build tool referenced in config files, not a runtime import. False positive for this toolchain package. | ai | |
| phantom-deps | phantom-dep:turbo | AI (phantom-deps): turbo is a build orchestration tool used as a binary, not a runtime import. False positive for this monorepo toolchain package. | ai | |
| phantom-deps | phantom-dep:@swc/cli | AI (phantom-deps): @swc/cli is a build tool referenced in scripts/config, not a runtime import. False positive for this toolchain package. | ai | |
| phantom-deps | phantom-dep:@swc/core | AI (phantom-deps): @swc/core is a build tool referenced in config files, not a runtime import. False positive for this toolchain package. | ai | |
| phantom-deps | phantom-dep:@autosoft/tsconfig | AI (phantom-deps): Same-org tsconfig package used as a build config reference, not a runtime import. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@autosoft/jest-preset | AI (phantom-deps): Same-org jest preset used in jest config, not a runtime import. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@autosoft/eslint-config | AI (phantom-deps): Same-org eslint config used in eslintConfig field, not a runtime import. Stable false positive. | ai | |
| phantom-deps | phantom-dep:npm-package-json-lint-config-auto | AI (phantom-deps): Lint config package referenced in npmpackagejsonlint config field, not a runtime import. Stable false positive. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.2.15 | 31 / 2 | |
| 0.2.14 | 31 / 1 | |
| 0.2.12 | 31 / 1 | |
| 0.2.11 | 31 / 1 | |
| 0.2.10 | 30 / 1 | |
| 0.2.9 | 30 / 1 | |
| 0.2.8 | 30 / 1 | |
| 0.2.7 | 30 / 1 | |
| 0.2.6 | 30 / 1 | |
| 0.2.5 | 27 / 1 | |
| 0.1.2 | 22 / 0 | |
| 0.1.1 | 22 / 0 | |
| 0.1.0 | 22 / 0 |
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.