@soonspacejs/plugin-fds
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
Keywords
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.15.15 | 0 / 0 | |
| 2.15.14 | 0 / 0 | |
| 2.15.13 | 0 / 0 | |
| 2.15.12 | 0 / 0 | |
| 2.15.11 | 0 / 0 | |
| 2.15.10 | 0 / 0 | |
| 2.15.9 | 0 / 0 | |
| 2.15.8 | 0 / 0 | |
| 2.15.4 | 0 / 0 | |
| 2.15.2 | 0 / 0 | |
| 2.15.1 | 0 / 0 |
v2.15.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 (chjxx) than the most recent previously approved version (jiangqi) on 2026-07-24, but chjxx 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.
v2.15.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.13
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 (jiangqi) than the most recent previously approved version (chjxx) on 2026-07-08, but jiangqi 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.
v2.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.