@playcademy/vite-plugin
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@playcademy/utils | AI (phantom-deps): Same-org scoped dependency; likely used indirectly or via build tooling. Consistent with internal utility extraction pattern across @playcademy packages. | ai | |
| dependencies | unvetted-dep:playcademy | AI (dependencies): playcademy is a first-party dependency from the same @playcademy organization; expected in this SDK ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package has 128 versions, 347 days of history, and 1.9k weekly downloads — metadata gaps are hygiene issues, not malice indicators. | ai | |
| phantom-deps | phantom-dep:archiver | AI (phantom-deps): archiver is a declared runtime dependency in a Vite plugin; phantom-dep false positive common when deps are used in build scripts or bundled indirectly. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): picocolors is a declared runtime dependency; phantom-dep false positive common in plugin packages where usage may be indirect or bundled. | ai | |
| phantom-deps | phantom-dep:playcademy | AI (phantom-deps): playcademy is a first-party ecosystem dependency; phantom-dep false positive expected for platform integration packages. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 0.3.3 | 3 / 9 | |
| 0.3.2 | 3 / 9 | |
| 0.3.1 | 3 / 9 | |
| 0.3.0 | 3 / 9 | |
| 0.2.34 | 3 / 9 | |
| 0.2.33 | 3 / 9 | |
| 0.2.32 | 3 / 9 | |
| 0.2.31 | 3 / 9 | |
| 0.2.30 | 3 / 9 | |
| 0.2.29 | 3 / 9 | |
| 0.2.28 | 3 / 9 | |
| 0.2.27 | 3 / 9 | |
| 0.2.26 | 3 / 9 | |
| 0.2.25 | 3 / 9 | |
| 0.2.24 | 3 / 9 | |
| 0.2.23 | 3 / 9 | |
| 0.2.22 | 3 / 9 | |
| 0.2.21 | 3 / 9 | |
| 0.2.20 | 3 / 9 | |
| 0.2.19 | 3 / 5 | |
| 0.2.18 | 3 / 5 | |
| 0.2.17 | 3 / 5 | |
| 0.2.16 | 3 / 5 | |
| 0.2.15 | 3 / 5 | |
| 0.2.14 | 3 / 5 | |
| 0.2.13 | 3 / 5 | |
| 0.2.12 | 3 / 5 | |
| 0.2.11 | 3 / 5 | |
| 0.2.10 | 3 / 5 | |
| 0.2.9 | 3 / 5 | |
| 0.2.8 | 3 / 5 | |
| 0.2.6 | 3 / 5 | |
| 0.2.5 | 3 / 5 | |
| 0.2.4 | 3 / 5 | |
| 0.2.3 | 3 / 5 | |
| 0.2.1 | 4 / 4 | |
| 0.2.0 | 4 / 4 | |
| 0.1.40 | 3 / 4 | |
| 0.1.38 | 3 / 4 | |
| 0.1.37 | 3 / 4 | |
| 0.1.36 | 3 / 4 | |
| 0.1.35 | 3 / 4 | |
| 0.1.34 | 3 / 4 | |
| 0.1.33 | 3 / 4 | |
| 0.1.32 | 3 / 4 | |
| 0.1.31 | 3 / 4 | |
| 0.1.30 | 3 / 4 | |
| 0.1.29 | 3 / 4 | |
| 0.1.28 | 3 / 4 | |
| 0.1.27 | 3 / 4 | |
| 0.1.25 | 3 / 5 |
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.