@playdrop/playdrop-cli
Official Playdrop CLI for publishing browser games, creator apps, and AI-generated game assets on playdrop.ai
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo CLI with 53 published versions; missing gitHead reflects CI environment change, not tampering. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ajv and semver are canonical, well-vetted packages; addition is benign for a CLI tool. | ai | |
| dependencies | unvetted-dep:@playdrop/ai-client | AI (dependencies): Monorepo file: dep bundled at publish time; not a registry bypass risk. | ai | |
| dependencies | unvetted-dep:@playdrop/vox-three | AI (dependencies): Monorepo file: dep bundled at publish time; not a registry bypass risk. | ai | |
| dependencies | unvetted-dep:@playdrop/api-client | AI (dependencies): Monorepo file: dep bundled at publish time; not a registry bypass risk. | ai | |
| dependencies | unvetted-dep:@playdrop/boxel-core | AI (dependencies): Monorepo file: dep bundled at publish time; not a registry bypass risk. | ai | |
| dependencies | unvetted-dep:@playdrop/boxel-three | AI (dependencies): Monorepo file: dep bundled at publish time; not a registry bypass risk. | ai | |
| npm-metadata | url-dep:@playdrop/types | AI (npm-metadata): Intentional monorepo bundling pattern; siblings are included in published tarball. | ai | |
| dependencies | unvetted-dep:@playdrop/types | AI (dependencies): Monorepo file: dep bundled at publish time; not a registry bypass risk. | ai | |
| npm-metadata | url-dep:@playdrop/ai-client | AI (npm-metadata): Intentional monorepo bundling pattern; siblings are included in published tarball. | ai | |
| npm-metadata | url-dep:@playdrop/vox-three | AI (npm-metadata): Intentional monorepo bundling pattern; siblings are included in published tarball. | ai | |
| npm-metadata | url-dep:@playdrop/api-client | AI (npm-metadata): Intentional monorepo bundling pattern; siblings are included in published tarball. | ai | |
| npm-metadata | url-dep:@playdrop/boxel-core | AI (npm-metadata): Intentional monorepo bundling pattern; siblings are included in published tarball. | ai | |
| npm-metadata | url-dep:@playdrop/boxel-three | AI (npm-metadata): Intentional monorepo bundling pattern; siblings are included in published tarball. | ai | |
| npm-metadata | url-dep:@playdrop/config | AI (npm-metadata): Intentional monorepo bundling pattern; siblings are included in published tarball. | ai | |
| dependencies | unvetted-dep:@playdrop/config | AI (dependencies): Monorepo file: dep bundled at publish time; not a registry bypass risk. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.9.3 | 14 / 2 | |
| 0.9.2 | 14 / 2 | |
| 0.9.1 | 14 / 2 | |
| 0.9.0 | 14 / 2 | |
| 0.8.8 | 14 / 2 | |
| 0.8.6 | 14 / 2 | |
| 0.8.3 | 14 / 2 | |
| 0.8.2 | 14 / 2 | |
| 0.8.0 | 14 / 2 | |
| 0.7.26 | 14 / 2 | |
| 0.7.25 | 14 / 2 | |
| 0.6.2 | 14 / 2 | |
| 0.5.6 | 14 / 2 | |
| 0.5.3 | 14 / 2 | |
| 0.5.2 | 12 / 2 | |
| 0.5.1 | 12 / 2 | |
| 0.5.0 | 12 / 2 |
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
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.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: playdrop_admin.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: playdrop_admin.
v0.8.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: playdrop_admin.
v0.8.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: playdrop_admin.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: playdrop_admin.
v0.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.