@lukso/lsp7-contracts
Package for the LSP7 Digital Asset standard
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is backed by SLSA provenance attestation; consistent with CI/CD automation for this org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD pipeline migration; SLSA attestation confirms legitimate release process. | ai | |
| phantom-deps | phantom-dep:@lukso/lsp4-contracts | AI (phantom-deps): Solidity contract dependency; not imported in JS but used in .sol files — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lukso/lsp1-contracts | AI (phantom-deps): Solidity contract dependency; not imported in JS but used in .sol files — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lukso/lsp17contractextension-contracts | AI (phantom-deps): Solidity contract dependency; not imported in JS but used in .sol files — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/contracts | AI (phantom-deps): OpenZeppelin Solidity contracts; referenced in .sol files not JS — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lukso/lsp2-contracts | AI (phantom-deps): Solidity contract dependency; not imported in JS but used in .sol files — stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 5 / 6 | |
| 0.17.3 | 5 / 6 | |
| 0.16.8 | 5 / 0 | |
| 0.16.6 | 5 / 0 | |
| 0.16.5 | 5 / 0 |
v0.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.