← Home

@lukso/lsp0-contracts

npm Repository Homepage

Package for the LSP0ERC725Account standard

4
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.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from lukso-network to GitHub Actions is consistent with SLSA-attested CI/CD publishing; official org repo confirmed. ai
publish-pattern dormant-publish AI (publish-pattern): 340-day gap explained by infrequent release cadence; SLSA attestation and org continuity reduce takeover risk. ai
phantom-deps phantom-dep:@lukso/lsp14-contracts AI (phantom-deps): Solidity import; JS scanner can't detect .sol imports. ai
phantom-deps phantom-dep:@lukso/lsp20-contracts AI (phantom-deps): Solidity import; JS scanner can't detect .sol imports. ai
phantom-deps phantom-dep:@lukso/lsp1-contracts AI (phantom-deps): Solidity import; JS scanner can't detect .sol imports. ai
phantom-deps phantom-dep:@erc725/smart-contracts AI (phantom-deps): Solidity import; JS scanner can't detect .sol imports. ai
phantom-deps phantom-dep:@openzeppelin/contracts AI (phantom-deps): Solidity import; JS scanner can't detect .sol imports. ai
phantom-deps phantom-dep:@lukso/lsp17contractextension-contracts AI (phantom-deps): Solidity import; JS scanner can't detect .sol imports. ai
phantom-deps phantom-dep:@lukso/lsp2-contracts AI (phantom-deps): Solidity import; JS scanner can't detect .sol imports. ai

Versions (showing 4 of 4)

Version Deps Published
0.16.3 7 / 4
0.15.5 7 / 0
0.15.3 7 / 0
0.15.2 7 / 0

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.5

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.

v0.15.3

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.

v0.15.2

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.