@playcademy/sdk
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
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.11.0 | 0 / 13 | |
| 0.10.0 | 0 / 13 | |
| 0.9.0 | 0 / 13 | |
| 0.8.0 | 0 / 13 | |
| 0.7.3 | 0 / 13 | |
| 0.7.2 | 0 / 13 | |
| 0.7.1 | 0 / 13 | |
| 0.7.0 | 0 / 13 | |
| 0.6.0 | 0 / 13 | |
| 0.5.0 | 0 / 13 | |
| 0.4.0 | 0 / 13 | |
| 0.3.6 | 0 / 13 | |
| 0.3.5 | 0 / 13 | |
| 0.3.4 | 0 / 13 | |
| 0.3.3 | 0 / 13 | |
| 0.3.2 | 0 / 13 | |
| 0.3.1 | 0 / 14 | |
| 0.3.0 | 0 / 14 | |
| 0.2.14 | 0 / 14 | |
| 0.2.13 | 0 / 14 | |
| 0.2.12 | 0 / 14 | |
| 0.2.11 | 0 / 14 | |
| 0.2.10 | 0 / 14 | |
| 0.2.9 | 0 / 14 | |
| 0.2.8 | 0 / 14 | |
| 0.2.7 | 0 / 14 | |
| 0.2.6 | 0 / 14 | |
| 0.2.5 | 0 / 14 | |
| 0.2.4 | 0 / 14 | |
| 0.2.3 | 0 / 14 | |
| 0.2.2 | 0 / 13 | |
| 0.2.1 | 0 / 13 | |
| 0.2.0 | 0 / 13 | |
| 0.1.18 | 0 / 13 | |
| 0.1.17 | 0 / 13 | |
| 0.1.16 | 0 / 13 | |
| 0.1.15 | 0 / 13 | |
| 0.1.14 | 0 / 13 | |
| 0.1.13 | 0 / 14 | |
| 0.1.12 | 0 / 14 | |
| 0.1.11 | 0 / 14 | |
| 0.1.10 | 0 / 14 | |
| 0.1.9 | 0 / 14 | |
| 0.1.8 | 0 / 14 | |
| 0.1.7 | 0 / 14 | |
| 0.1.6 | 0 / 14 | |
| 0.1.5 | 0 / 14 | |
| 0.1.4 | 0 / 14 | |
| 0.1.3 | 0 / 14 | |
| 0.1.2 | 0 / 14 | |
| 0.1.1 | 0 / 14 |
v0.11.0
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.