@soonspacejs/plugin-sbmz-loader
Sbmz-loader plugin for SoonSpace.js
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 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 |
v2.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.