@soonspacejs/plugin-tiles
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 51 of 124)
| 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.1 | 0 / 0 | |
| 2.15.0 | 0 / 0 | |
| 2.14.37 | 0 / 0 | |
| 2.14.35 | 0 / 0 | |
| 2.14.34 | 0 / 0 | |
| 2.14.33 | 0 / 0 | |
| 2.14.32 | 0 / 0 | |
| 2.14.31 | 0 / 0 | |
| 2.14.30 | 0 / 0 | |
| 2.14.29 | 0 / 0 | |
| 2.14.28 | 0 / 0 | |
| 2.14.27 | 0 / 0 | |
| 2.14.26 | 0 / 0 | |
| 2.14.24 | 0 / 0 | |
| 2.14.23 | 0 / 0 | |
| 2.14.13 | 0 / 0 | |
| 2.14.12 | 0 / 0 | |
| 2.14.11 | 0 / 0 | |
| 2.14.10 | 0 / 0 | |
| 2.14.9 | 0 / 0 | |
| 2.14.8 | 0 / 0 | |
| 2.14.7 | 0 / 0 | |
| 2.14.6 | 0 / 0 | |
| 2.14.5 | 0 / 0 | |
| 2.14.2 | 0 / 0 | |
| 2.14.1 | 0 / 0 | |
| 2.14.0 | 0 / 0 | |
| 2.13.17 | 0 / 0 | |
| 2.13.12 | 0 / 0 | |
| 2.13.11 | 0 / 0 | |
| 2.13.10 | 0 / 0 | |
| 2.13.9 | 0 / 0 | |
| 2.13.8 | 0 / 0 | |
| 2.13.6 | 0 / 0 | |
| 2.13.5 | 0 / 0 | |
| 2.13.4 | 0 / 0 | |
| 2.13.2 | 0 / 0 | |
| 2.13.1 | 0 / 0 | |
| 2.13.0 | 0 / 0 | |
| 2.12.2 | 0 / 0 | |
| 2.12.1 | 0 / 0 | |
| 2.12.0 | 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.13.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 (jiangqi) than the most recent previously approved version (guobinyong) on 2025-04-14, 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.13.4
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 (guobinyong) than the most recent previously approved version (jiangqi) on 2025-04-10, but guobinyong 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.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.