← Home

@solana-program/token-2022

npm Repository Homepage

JavaScript client for the Token 2022 program

21
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 No source commit

Maintainers

joncinquesolana-devs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Migrated to GitHub Actions CI/CD with SLSA provenance; legitimate transition for this org. ai

Versions (showing 21 of 21)

Version Deps Published
0.13.0 2 / 17
0.12.0 2 / 17
0.11.0 2 / 15
0.10.0 2 / 15
0.9.0 0 / 14
0.8.0 0 / 14
0.7.0 0 / 14
0.6.1 0 / 14
0.6.0 0 / 14
0.5.0 0 / 14
0.4.2 0 / 14
0.4.1 0 / 14
0.4.0 0 / 14
0.3.4 0 / 14
0.3.3 0 / 14
0.3.2 0 / 14
0.3.1 0 / 14
0.3.0 0 / 14
0.2.1 0 / 14
0.2.0 0 / 15
0.1.0 0 / 15

v0.13.0

1 finding
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.4.0

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: solana-devs → joncinque (on 2025-03-03, known maintainer) provenance

This version was published by a different npm account (joncinque) than the most recent previously approved version (solana-devs) on 2025-03-03, but joncinque 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.3.4

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 → solana-devs (on 2025-01-07, known maintainer) provenance

This version was published by a different npm account (solana-devs) than the most recent previously approved version (lorisleiva) on 2025-01-07, but solana-devs 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.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.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.1.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.