@playcademy/sandbox No license 36 versions

@playcademy/sandbox

npm

Local development server for Playcademy game development

36

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

eli-goodinghbauerelpjulian

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@playcademy/constants	AI (phantom-deps): Same-org scoped package; likely used transitively, not directly imported in this package.	ai	2026/05/18
phantom-deps	phantom-dep:hono	AI (phantom-deps): Bundled CLI/server package; deps are compiled into dist/ output, so static import analysis won't find direct imports. Stable false positive for this build pattern.	ai	2026/04/25
phantom-deps	phantom-dep:jose	AI (phantom-deps): Bundled CLI/server package; deps are compiled into dist/ output, so static import analysis won't find direct imports. Stable false positive for this build pattern.	ai	2026/04/25
phantom-deps	phantom-dep:commander	AI (phantom-deps): Bundled CLI/server package; deps are compiled into dist/ output, so static import analysis won't find direct imports. Stable false positive for this build pattern.	ai	2026/04/25
phantom-deps	phantom-dep:picocolors	AI (phantom-deps): Bundled CLI/server package; deps are compiled into dist/ output, so static import analysis won't find direct imports. Stable false positive for this build pattern.	ai	2026/04/25
phantom-deps	phantom-dep:zod	AI (phantom-deps): Bundled CLI/server package; deps are compiled into dist/ output, so static import analysis won't find direct imports. Stable false positive for this build pattern.	ai	2026/04/25
phantom-deps	phantom-dep:drizzle-orm	AI (phantom-deps): Bundled CLI/server package; deps are compiled into dist/ output, so static import analysis won't find direct imports. Stable false positive for this build pattern.	ai	2026/04/25
phantom-deps	phantom-dep:json-colorizer	AI (phantom-deps): Bundled CLI/server package; deps are compiled into dist/ output, so static import analysis won't find direct imports. Stable false positive for this build pattern.	ai	2026/04/25
phantom-deps	phantom-dep:@electric-sql/pglite	AI (phantom-deps): Bundled CLI/server package; deps are compiled into dist/ output, so static import analysis won't find direct imports. Stable false positive for this build pattern.	ai	2026/04/25
dependencies	unvetted-dep:json-colorizer	AI (dependencies): json-colorizer is a legitimate, well-known terminal JSON colorization utility appropriate for a CLI dev tool. No malicious signals or advisories.	ai	2026/04/25
phantom-deps	phantom-dep:drizzle-kit	AI (phantom-deps): Bundled CLI/server package; deps are compiled into dist/ output, so static import analysis won't find direct imports. Stable false positive for this build pattern.	ai	2026/04/25

Versions (showing 36 of 36)

Version	Deps	Published
0.4.1	9 / 13	2026-05-17
0.4.0	9 / 13	2026-05-15
0.3.18	10 / 13	2026-05-11
0.3.17	10 / 13	2026-05-08
0.3.16	10 / 13	2026-04-13
0.3.15	10 / 14	2026-03-30
0.3.14	9 / 11	2026-01-12
0.3.13	9 / 11	2025-12-17
0.3.12	9 / 11	2025-12-16
0.3.11	9 / 11	2025-12-13
0.3.10	9 / 11	2025-12-12
0.3.9	9 / 11	2025-12-09
0.3.8	9 / 11	2025-12-08
0.3.7	9 / 9	2025-12-03
0.3.6	9 / 9	2025-11-28
0.3.5	9 / 9	2025-11-28
0.3.4	9 / 9	2025-11-28
0.3.2	9 / 10	2025-11-28
0.3.1	9 / 10	2025-11-28
0.3.0	9 / 10	2025-11-28
0.2.3	9 / 10	2025-11-27
0.2.2	9 / 10	2025-11-27
0.2.1	9 / 10	2025-11-27
0.2.0	9 / 10	2025-11-27
0.1.11	9 / 10	2025-11-03
0.1.10	9 / 10	2025-11-02
0.1.9	8 / 9	2025-10-23
0.1.8	8 / 9	2025-10-22
0.1.7	8 / 9	2025-10-20
0.1.6	8 / 9	2025-10-20
0.1.5	8 / 9	2025-10-20
0.1.4	8 / 9	2025-10-20
0.1.3	8 / 9	2025-10-20
0.1.2	9 / 9	2025-10-20
0.1.1	9 / 9	2025-10-17
0.1.0	8 / 8	2025-10-08

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.