@cityofzion/blockchain-service
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established org package with trusted publisher history; dormancy consistent with normal release cadence variation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with clear purpose; missing description is metadata gap, not malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Provenance adoption is sparse ecosystem-wide; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): Elliptic cryptography is core to blockchain services; pinned version is expected and appropriate for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.1.15 | 7 / 9 | |
| 3.1.14 | 7 / 9 | |
| 3.1.13 | 7 / 9 | |
| 3.1.12 | 7 / 9 | |
| 3.1.11 | 7 / 9 | |
| 3.1.10 | 7 / 9 | |
| 3.1.9 | 7 / 9 | |
| 3.1.7 | 7 / 9 | |
| 3.1.6 | 7 / 9 | |
| 3.1.2 | 7 / 9 | |
| 3.1.0 | 7 / 9 | |
| 3.0.6 | 7 / 9 | |
| 3.0.3 | 7 / 12 | |
| 3.0.0 | 7 / 12 | |
| 1.22.8 | 7 / 12 | |
| 1.22.5 | 7 / 12 | |
| 1.22.4 | 7 / 12 |
v3.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.