@cityofzion/bs-neo-legacy
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped org package with 117 versions; missing metadata is cosmetic, not indicative of spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established org package; missing description is a style issue, not a risk signal. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 3.1.14 | 5 / 7 | |
| 3.1.12 | 5 / 7 | |
| 3.1.9 | 4 / 7 | |
| 3.1.8 | 4 / 7 | |
| 3.1.7 | 4 / 7 | |
| 3.1.6 | 4 / 7 | |
| 3.1.5 | 4 / 7 | |
| 3.1.4 | 4 / 7 | |
| 3.1.3 | 4 / 7 | |
| 3.1.2 | 4 / 7 | |
| 3.1.1 | 4 / 7 | |
| 3.1.0 | 4 / 7 | |
| 3.0.6 | 4 / 7 | |
| 3.0.5 | 4 / 7 | |
| 3.0.4 | 4 / 10 | |
| 3.0.3 | 4 / 10 | |
| 3.0.2 | 4 / 10 | |
| 3.0.1 | 4 / 10 | |
| 3.0.0 | 4 / 10 | |
| 1.16.0 | 4 / 10 | |
| 1.15.1 | 4 / 10 | |
| 1.15.0 | 4 / 10 | |
| 1.14.5 | 4 / 10 | |
| 1.14.4 | 4 / 10 | |
| 1.14.3 | 4 / 10 | |
| 1.14.2 | 4 / 10 | |
| 1.14.1 | 4 / 10 | |
| 1.14.0 | 4 / 10 | |
| 1.13.9 | 4 / 10 |
v3.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.