@types/acorn
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @types/acorn is a legitimate DefinitelyTyped stub for the acorn JS parser; the Levenshtein match to 'cors' is a false positive with no semantic relationship. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is an intentionally minimal deprecated stub redirecting to acorn's bundled types; tiny payload, no README code, and no keywords are expected for this pattern. | ai | |
| phantom-deps | phantom-dep:acorn | AI (phantom-deps): acorn is listed as a dependency intentionally so this stub pulls in the real package; no direct import is expected in a stub/redirect package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.0.4 | 1 / 0 | |
| 6.0.3 | 1 / 0 | |
| 6.0.2 | 1 / 0 | |
| 6.0.1 | 1 / 0 | |
| 6.0.0 | 1 / 0 |
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.