@lukso/lsp26-contracts
Package for the LSP26 Follower System standard
3
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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 | no-provenance | AI (provenance): LUKSO org packages consistently lack Sigstore provenance; stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@lukso/lsp0-contracts | AI (phantom-deps): Same-org Solidity dependency; declared for Hardhat compilation, not direct JS import — stable false positive. | ai | |
| phantom-deps | phantom-dep:@lukso/lsp1-contracts | AI (phantom-deps): Same-org Solidity dependency; declared for Hardhat compilation, not direct JS import — stable false positive. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/contracts | AI (phantom-deps): OpenZeppelin Solidity contracts used via Hardhat config, not direct JS import — stable false positive for this package. | ai |
v0.1.5
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.