@lukso/lsp8-contracts
Package for the LSP8 Identifiable 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): Publisher changed to GitHub Actions with SLSA provenance attestation — standard CI/CD publishing migration for lukso-network org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by infrequent smart-contract library release cadence; SLSA attestation confirms legitimate CI publish. | ai | |
| phantom-deps | phantom-dep:@lukso/lsp4-contracts | AI (phantom-deps): Solidity dep consumed via Hardhat compiler, not JS import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@lukso/lsp1-contracts | AI (phantom-deps): Solidity dep consumed via Hardhat compiler, not JS import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@lukso/lsp17contractextension-contracts | AI (phantom-deps): Solidity dep consumed via Hardhat compiler, not JS import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/contracts | AI (phantom-deps): OpenZeppelin referenced in Hardhat/Solidity config; not a JS import; stable for this package. | ai | |
| phantom-deps | phantom-dep:@lukso/lsp2-contracts | AI (phantom-deps): Solidity dep consumed via Hardhat compiler, not JS import; stable pattern for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 5 / 6 | |
| 0.17.3 | 5 / 6 | |
| 0.16.7 | 5 / 0 | |
| 0.16.5 | 5 / 0 | |
| 0.16.4 | 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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.