← Home

@metaplex-foundation/mpl-toolbox

npm Repository Homepage
14
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

danenbm1nhanphanbrandontulsisvc01-metaplexdanenbmblockiosaurus

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from svc01-metaplex to GitHub Actions CI with SLSA provenance; legitimate CI migration. ai

Versions (showing 14 of 14)

Version Deps Published
0.11.4 0 / 19
0.11.3 0 / 19
0.11.2 0 / 19
0.11.1 0 / 19
0.10.0 0 / 19
0.9.4 0 / 19
0.9.2 0 / 19
0.9.1 0 / 19
0.9.0 0 / 19
0.8.1 0 / 19
0.8.0 0 / 19
0.7.0 0 / 19
0.6.1 0 / 19
0.6.0 0 / 19

v0.9.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: lorisleiva → svc01-metaplex (on 2024-02-01, known maintainer) provenance

This version was published by a different npm account (svc01-metaplex) than the most recent previously approved version (lorisleiva) on 2024-02-01, but svc01-metaplex is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

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

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

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.