@debridge-finance/solana-transaction-parser
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@coral-xyz/spl-token | AI (dependencies): Known Coral/Anchor ecosystem SPL token library; stable dependency for this Solana parser package. | ai | |
| dependencies | unvetted-dep:@solana/spl-type-length-value | AI (dependencies): Official @solana-scoped utility library; stable dependency for this Solana parser package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.4.1 | 8 / 23 | |
| 3.4.0 | 8 / 23 | |
| 3.3.1 | 8 / 23 | |
| 3.3.0 | 8 / 23 | |
| 3.2.3 | 8 / 23 | |
| 3.2.1 | 8 / 23 | |
| 3.2.0 | 8 / 23 | |
| 3.1.3 | 8 / 23 | |
| 3.1.2 | 8 / 23 | |
| 3.1.1 | 9 / 23 | |
| 3.1.0 | 9 / 23 | |
| 3.0.0 | 8 / 23 |
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.