@lukso/lsp5-contracts
Package for the LSP5 Received Assets standard
3
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
frozemanlukso-network
Keywords
LUKSOLSPBlockchainStandardsSmart ContractsEthereumEVMSolidity
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 consistent with SLSA-attested CI/CD pipeline from the official lukso-network org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-published release with SLSA provenance; consistent with infrequent but legitimate releases for a smart contracts library. | ai | |
| provenance | no-provenance | AI (provenance): Solidity/smart-contract library; missing provenance is common and not a meaningful risk signal here. | ai | |
| phantom-deps | phantom-dep:@erc725/smart-contracts | AI (phantom-deps): Referenced in config files (e.g. hardhat config) rather than JS imports; stable false positive for this package type. | ai |
v0.16.3
2 findings
HIGH
Publisher changed: lukso-network → GitHub Actions (on 2026-05-25)
provenance
This 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.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.