← Home

@lukso/lsp9-contracts

Package for the LSP9 Vault 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 to GitHub Actions publisher is confirmed legitimate by SLSA Sigstore attestation from the official org repo. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by CI/CD migration; SLSA attestation confirms publish integrity. ai
phantom-deps phantom-dep:@lukso/lsp1-contracts AI (phantom-deps): Solidity/Hardhat package; deps declared for compiler remappings, not JS imports. Stable pattern for this org. ai
phantom-deps phantom-dep:@lukso/lsp6-contracts AI (phantom-deps): Same as above — Hardhat remapping dependency, not a JS import. ai
phantom-deps phantom-dep:@erc725/smart-contracts AI (phantom-deps): Referenced in config files for Hardhat; not a JS import. Expected pattern. ai
phantom-deps phantom-dep:@openzeppelin/contracts AI (phantom-deps): OpenZeppelin Solidity contracts used via Hardhat remappings, not JS imports. ai

Versions (showing 4 of 4)

Version Deps Published
0.16.3 4 / 6
0.15.5 4 / 0
0.15.3 4 / 0
0.15.2 4 / 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.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.