@ibgib/ts-gib
11
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
wraiford
Keywords
ibgibdltblockchaingraph-database
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Publisher consistently publishes without provenance; stable pattern across 31 versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.5.32 | 1 / 0 | |
| 0.5.31 | 1 / 0 | |
| 0.5.30 | 1 / 0 | |
| 0.5.29 | 1 / 1 | |
| 0.5.28 | 1 / 1 | |
| 0.5.27 | 1 / 1 | |
| 0.5.26 | 1 / 1 | |
| 0.5.25 | 1 / 1 | |
| 0.5.24 | 1 / 1 | |
| 0.5.23 | 1 / 1 | |
| 0.5.21 | 1 / 1 |
v0.5.21
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.