@helium/anchor-resolvers
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publisher is backed by SLSA Sigstore attestation; consistent with org automation migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-attested publish with no code changes; low risk of takeover given SLSA provenance. | ai |
Versions (showing 90 of 90)
| Version | Deps | Published |
|---|---|---|
| 0.11.16 | 2 / 3 | |
| 0.11.15 | 2 / 3 | |
| 0.11.14 | 2 / 3 | |
| 0.11.13 | 2 / 3 | |
| 0.11.12 | 2 / 3 | |
| 0.11.11 | 2 / 3 | |
| 0.11.10 | 2 / 3 | |
| 0.11.9 | 2 / 3 | |
| 0.11.8 | 2 / 3 | |
| 0.11.7 | 2 / 3 | |
| 0.11.6 | 2 / 3 | |
| 0.11.5 | 2 / 3 | |
| 0.11.4 | 2 / 3 | |
| 0.11.3 | 2 / 3 | |
| 0.11.2 | 2 / 3 | |
| 0.11.1 | 2 / 3 | |
| 0.11.0 | 2 / 3 | |
| 0.10.35 | 2 / 3 | |
| 0.10.34 | 2 / 3 | |
| 0.10.33 | 2 / 3 | |
| 0.10.32 | 2 / 3 | |
| 0.10.31 | 2 / 3 | |
| 0.10.30 | 2 / 3 | |
| 0.10.29 | 2 / 3 | |
| 0.10.28 | 2 / 3 | |
| 0.10.27 | 2 / 3 | |
| 0.10.26 | 2 / 3 | |
| 0.10.25 | 2 / 3 | |
| 0.10.24 | 2 / 3 | |
| 0.10.23 | 2 / 3 | |
| 0.10.22 | 2 / 3 | |
| 0.10.21 | 2 / 3 | |
| 0.10.20 | 2 / 3 | |
| 0.10.19 | 2 / 3 | |
| 0.10.18 | 2 / 3 | |
| 0.10.17 | 2 / 3 | |
| 0.10.16 | 2 / 3 | |
| 0.10.15 | 2 / 3 | |
| 0.10.14 | 2 / 3 | |
| 0.10.13 | 2 / 3 | |
| 0.10.12 | 2 / 3 | |
| 0.10.11 | 2 / 3 | |
| 0.10.10 | 2 / 3 | |
| 0.10.9 | 2 / 3 | |
| 0.10.8 | 2 / 3 | |
| 0.10.7 | 2 / 3 | |
| 0.10.6 | 2 / 3 | |
| 0.10.5 | 2 / 3 | |
| 0.10.4 | 2 / 3 | |
| 0.10.3 | 2 / 3 | |
| 0.10.2 | 2 / 3 | |
| 0.10.1 | 2 / 3 | |
| 0.10.0 | 2 / 3 | |
| 0.9.34 | 2 / 3 | |
| 0.9.33 | 2 / 3 | |
| 0.9.32 | 2 / 3 | |
| 0.9.31 | 2 / 3 | |
| 0.9.30 | 2 / 3 | |
| 0.9.29 | 2 / 3 | |
| 0.9.28 | 2 / 3 | |
| 0.9.27 | 2 / 3 | |
| 0.9.26 | 2 / 3 | |
| 0.9.25 | 2 / 3 | |
| 0.9.24 | 2 / 3 | |
| 0.9.23 | 2 / 3 | |
| 0.9.22 | 2 / 3 | |
| 0.9.21 | 2 / 3 | |
| 0.9.20 | 2 / 3 | |
| 0.9.19 | 2 / 3 | |
| 0.9.18 | 2 / 3 | |
| 0.9.17 | 2 / 3 | |
| 0.9.16 | 2 / 3 | |
| 0.9.15 | 2 / 3 | |
| 0.9.14 | 2 / 3 | |
| 0.9.13 | 2 / 3 | |
| 0.9.12 | 2 / 3 | |
| 0.9.11 | 2 / 3 | |
| 0.9.10 | 2 / 3 | |
| 0.9.9 | 2 / 3 | |
| 0.9.8 | 2 / 3 | |
| 0.9.7 | 2 / 3 | |
| 0.9.6 | 2 / 3 | |
| 0.9.5 | 2 / 3 | |
| 0.9.4 | 2 / 3 | |
| 0.9.3 | 2 / 3 | |
| 0.9.2 | 2 / 3 | |
| 0.9.1 | 2 / 3 | |
| 0.9.0 | 2 / 3 | |
| 0.8.8 | 2 / 3 | |
| 0.8.7 | 2 / 3 |
v0.10.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bryhelium) than the most recent previously approved version (nhelium) on 2024-10-29, but bryhelium 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.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nhelium) than the most recent previously approved version (bryhelium) on 2024-10-29, but nhelium 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.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nhelium) than the most recent previously approved version (bryhelium) on 2024-10-29, but nhelium 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.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bryhelium) than the most recent previously approved version (nhelium) on 2024-10-28, but bryhelium 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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.