@particle-network/chains
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is a chain's blockExplorerUrl metadata entry, not an exfil endpoint. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): All flagged URLs are legitimate blockchain RPC/explorer endpoints in a chain config package; pattern is stable across versions. | ai |
Versions (showing 51 of 100)
| Version | Deps | Published |
|---|---|---|
| 1.14.15 | 0 / 9 | |
| 1.8.3 | 0 / 9 | |
| 1.8.2 | 0 / 9 | |
| 1.8.1 | 0 / 9 | |
| 1.8.0 | 0 / 9 | |
| 1.7.9 | 0 / 9 | |
| 1.7.8 | 0 / 9 | |
| 1.7.7 | 0 / 9 | |
| 1.7.6 | 0 / 9 | |
| 1.7.5 | 0 / 9 | |
| 1.7.4 | 0 / 9 | |
| 1.7.3 | 0 / 9 | |
| 1.7.2 | 0 / 9 | |
| 1.7.1 | 0 / 9 | |
| 1.7.0 | 0 / 9 | |
| 1.6.9 | 0 / 9 | |
| 1.6.8 | 0 / 9 | |
| 1.6.7 | 0 / 9 | |
| 1.6.6 | 0 / 9 | |
| 1.6.5 | 0 / 9 | |
| 1.6.4 | 0 / 9 | |
| 1.6.3 | 0 / 9 | |
| 1.6.2 | 0 / 9 | |
| 1.6.1 | 0 / 9 | |
| 1.6.0 | 0 / 9 | |
| 1.5.12 | 0 / 9 | |
| 1.5.11 | 0 / 9 | |
| 1.5.10 | 0 / 9 | |
| 1.5.9 | 0 / 9 | |
| 1.5.8 | 0 / 9 | |
| 1.5.7 | 0 / 9 | |
| 1.5.6 | 0 / 9 | |
| 1.5.5 | 0 / 9 | |
| 1.5.4 | 0 / 9 | |
| 1.5.3 | 0 / 9 | |
| 1.5.2 | 0 / 9 | |
| 1.5.1 | 0 / 9 | |
| 1.5.0 | 0 / 9 | |
| 1.4.16 | 0 / 9 | |
| 1.4.15 | 0 / 9 | |
| 1.4.14 | 0 / 9 | |
| 1.4.13 | 0 / 9 | |
| 1.4.12 | 0 / 9 | |
| 1.4.11 | 0 / 9 | |
| 1.4.10 | 0 / 9 | |
| 1.4.9 | 0 / 9 | |
| 1.4.8 | 0 / 9 | |
| 1.4.7 | 0 / 9 | |
| 1.4.6 | 0 / 9 | |
| 1.4.5 | 0 / 9 | |
| 1.4.4 | 0 / 9 |
v1.14.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
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 (particle-web3) than the most recent previously approved version (wlasd5688) on 2024-11-14, but particle-web3 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.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
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 (wlasd5688) than the most recent previously approved version (particle-web3) on 2024-10-10, but wlasd5688 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.
v1.7.5
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 (wlasd5688) than the most recent previously approved version (particle-web3) on 2024-10-09, but wlasd5688 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.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
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 (particle-web3) than the most recent previously approved version (wlasd5688) on 2024-10-08, but particle-web3 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.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.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 (particle-web3) than the most recent previously approved version (wlasd5688) on 2024-09-29, but particle-web3 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.
v1.6.8
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 (wlasd5688) than the most recent previously approved version (particle-web3) on 2024-08-26, but wlasd5688 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.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
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 (particle-web3) than the most recent previously approved version (wlasd5688) on 2024-08-15, but particle-web3 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.
v1.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
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 (wlasd5688) than the most recent previously approved version (particle-web3) on 2024-06-27, but wlasd5688 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.
v1.5.2
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 (wlasd5688) than the most recent previously approved version (particle-web3) on 2024-06-25, but wlasd5688 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.
v1.5.1
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 (particle-web3) than the most recent previously approved version (wlasd5688) on 2024-06-24, but particle-web3 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.
v1.5.0
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 (particle-web3) than the most recent previously approved version (wlasd5688) on 2024-06-21, but particle-web3 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.
v1.4.16
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 (wlasd5688) than the most recent previously approved version (particle-web3) on 2024-06-18, but wlasd5688 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.
v1.4.15
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 (wlasd5688) than the most recent previously approved version (particle-web3) on 2024-06-18, but wlasd5688 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.
v1.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.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 (particle-web3) than the most recent previously approved version (wlasd5688) on 2024-05-29, but particle-web3 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.
v1.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.