@terminal3/bbs_vc
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding used for BBS/DID public key encoding — standard cryptographic operation in this library. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): Type-only package; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/jsonld | AI (phantom-deps): Type-only package; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:multiformats | AI (phantom-deps): Referenced in config files; indirect transitive use is expected in multibase/multicodec workflows. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.2.36 | 15 / 0 | |
| 0.2.35 | 15 / 0 | |
| 0.2.33 | 15 / 0 | |
| 0.2.32 | 15 / 0 | |
| 0.2.31 | 15 / 0 | |
| 0.2.30 | 15 / 0 | |
| 0.2.29 | 15 / 0 | |
| 0.2.28 | 15 / 0 | |
| 0.2.27 | 15 / 0 | |
| 0.2.26 | 15 / 0 | |
| 0.2.25 | 15 / 0 | |
| 0.2.24 | 15 / 0 |
v0.2.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.