playcademy
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/edge-play | AI (phantom-deps): Sibling monorepo package; indirect usage expected. | ai | |
| phantom-deps | phantom-dep:colorette | AI (phantom-deps): Same as above — CLI tooling with bundled deps. | ai | |
| phantom-deps | phantom-dep:json-colorizer | AI (phantom-deps): Same as above — CLI tooling with bundled deps. | ai | |
| phantom-deps | phantom-dep:@hono/node-server | AI (phantom-deps): Used indirectly via bundled CLI; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): CLI prompts dependency; bundled usage pattern triggers phantom-dep heuristic. | ai | |
| phantom-deps | phantom-dep:@playcademy/utils | AI (phantom-deps): Sibling monorepo package; indirect usage expected. | ai | |
| phantom-deps | phantom-dep:chokidar | AI (phantom-deps): CLI tool with config-file-driven deps; phantom-dep heuristic fires on bundled/indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): hono is a legitimate web framework; phantom detection is a false positive for this build-tool/CLI package that bundles deps via esbuild. | ai | |
| dependencies | unvetted-dep:miniflare | AI (dependencies): Miniflare is Cloudflare's official local Workers simulator; its use is consistent with this package's Cloudflare Workers-based tooling purpose. | ai | |
| phantom-deps | phantom-dep:open | AI (phantom-deps): open is a legitimate declared dependency; phantom detection likely reflects indirect usage in CLI code not statically traced. | ai | |
| phantom-deps | phantom-dep:dedent | AI (phantom-deps): dedent is a legitimate declared dependency; phantom detection likely reflects indirect usage not statically traced. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is a legitimate declared dependency for CLI tooling; phantom detection likely reflects indirect usage not statically traced. | ai |
Versions (showing 51 of 149)
| Version | Deps | Published |
|---|---|---|
| 0.23.0 | 16 / 22 | |
| 0.22.1 | 16 / 22 | |
| 0.22.0 | 16 / 22 | |
| 0.21.0 | 16 / 22 | |
| 0.20.0 | 16 / 22 | |
| 0.19.8 | 16 / 22 | |
| 0.19.7 | 16 / 22 | |
| 0.19.6 | 16 / 22 | |
| 0.19.5 | 16 / 22 | |
| 0.19.4 | 16 / 22 | |
| 0.19.3 | 16 / 22 | |
| 0.19.2 | 16 / 22 | |
| 0.19.1 | 16 / 22 | |
| 0.19.0 | 16 / 22 | |
| 0.18.9 | 16 / 20 | |
| 0.18.8 | 16 / 21 | |
| 0.18.7 | 16 / 21 | |
| 0.18.6 | 16 / 21 | |
| 0.18.5 | 16 / 21 | |
| 0.18.4 | 16 / 21 | |
| 0.18.3 | 16 / 21 | |
| 0.18.2 | 16 / 21 | |
| 0.18.1 | 16 / 21 | |
| 0.18.0 | 16 / 21 | |
| 0.17.5 | 16 / 21 | |
| 0.17.4 | 16 / 13 | |
| 0.17.3 | 16 / 13 | |
| 0.17.2 | 16 / 13 | |
| 0.17.1 | 16 / 11 | |
| 0.17.0 | 16 / 11 | |
| 0.16.17 | 16 / 11 | |
| 0.16.16 | 16 / 11 | |
| 0.16.15 | 16 / 11 | |
| 0.16.14 | 16 / 11 | |
| 0.16.13 | 16 / 11 | |
| 0.16.12 | 16 / 11 | |
| 0.16.11 | 16 / 11 | |
| 0.16.10 | 16 / 11 | |
| 0.16.9 | 16 / 11 | |
| 0.16.8 | 16 / 11 | |
| 0.16.7 | 16 / 11 | |
| 0.16.6 | 16 / 11 | |
| 0.16.5 | 16 / 11 | |
| 0.16.4 | 16 / 11 | |
| 0.16.3 | 16 / 11 | |
| 0.16.2 | 16 / 11 | |
| 0.16.1 | 16 / 11 | |
| 0.16.0 | 16 / 11 | |
| 0.15.6 | 16 / 11 | |
| 0.15.5 | 16 / 11 | |
| 0.15.4 | 16 / 11 |
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.