@lukso/lsp4-contracts
Package for the LSP4 Digital Asset Metadata 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 from lukso-network to GitHub Actions is consistent with SLSA-attested CI/CD publishing; same org repo confirmed. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms legitimate CI publish; dormancy explained by infrequent release cadence for a smart contracts package. | ai | |
| provenance | no-provenance | AI (provenance): Established LUKSO org package; missing provenance is common and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:@erc725/smart-contracts-v8 | AI (phantom-deps): Alias dependency used in config/build tooling; not directly imported in JS but legitimately declared. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.17.3 | 2 / 4 | |
| 0.16.7 | 2 / 0 | |
| 0.16.5 | 2 / 0 | |
| 0.16.4 | 2 / 0 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.