@celo/ledger-token-signer
13
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
app-tooling
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:lib/cjs/data.d.ts | AI (source-diff): Long base64 string is Ledger token metadata (currency codes + DER signatures); stable pattern for this package. | ai | |
| source-diff | encoded-string-file:lib/cjs/data.js | AI (source-diff): Same Ledger token metadata blob; benign for this package. | ai | |
| source-diff | encoded-string-file:lib/data.ts | AI (source-diff): Same Ledger token metadata blob; benign for this package. | ai | |
| source-diff | encoded-string-file:lib/mjs/data.d.ts | AI (source-diff): Same Ledger token metadata blob; benign for this package. | ai | |
| source-diff | encoded-string-file:lib/mjs/data.js | AI (source-diff): Same Ledger token metadata blob; benign for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped Celo utility package; missing metadata is cosmetic, not indicative of malice. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 0 / 12 | |
| 0.14.0 | 0 / 12 | |
| 0.13.0 | 0 / 12 | |
| 0.12.0 | 0 / 12 | |
| 0.11.0 | 0 / 12 | |
| 0.10.0 | 0 / 12 | |
| 0.9.0 | 0 / 12 | |
| 0.8.0 | 0 / 12 | |
| 0.7.0 | 0 / 12 | |
| 0.6.0 | 0 / 12 | |
| 0.5.0 | 0 / 12 | |
| 0.2.0 | 0 / 11 | |
| 0.1.0 | 0 / 9 |
v0.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.