goldstein
JavaScript with no limits
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:acorn-loose | AI (phantom-deps): acorn-loose is explicitly declared in package.json dependencies; phantom-dep heuristic misfires here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 7.3.2 | 11 / 17 | |
| 7.3.1 | 11 / 17 | |
| 7.3.0 | 11 / 17 | |
| 7.2.0 | 11 / 17 | |
| 7.1.0 | 11 / 17 | |
| 7.0.4 | 10 / 17 | |
| 7.0.3 | 10 / 18 | |
| 7.0.2 | 10 / 18 | |
| 7.0.1 | 10 / 18 | |
| 7.0.0 | 10 / 18 | |
| 6.1.2 | 10 / 18 | |
| 6.1.1 | 10 / 18 |
v7.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.