@playcraft/common
PlayCraft monorepo 内部共享库，给 CLI Agent / Backend / Realtime / Messenger 提供可复用的通用能力。
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance has been present across versions; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:ot-text | AI (dependencies): ot-text is a well-known ShareDB operational-transform type; legitimate dep for this package's use case. | ai | |
| dependencies | unvetted-dep:@teamwork/websocket-json-stream | AI (dependencies): Standard ShareDB companion library from @teamwork; legitimate for this collaborative-editing package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fuse.js is a well-established fuzzy-search library with no known malicious history. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal/monorepo shared library; missing repo URL and sparse README are expected for this type of package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.0.32 | 10 / 6 | |
| 0.0.31 | 10 / 6 | |
| 0.0.27 | 10 / 6 | |
| 0.0.26 | 10 / 6 | |
| 0.0.25 | 10 / 6 | |
| 0.0.24 | 10 / 6 | |
| 0.0.21 | 10 / 6 | |
| 0.0.20 | 10 / 6 | |
| 0.0.19 | 10 / 6 | |
| 0.0.18 | 10 / 6 | |
| 0.0.17 | 10 / 6 | |
| 0.0.12 | 9 / 6 | |
| 0.0.11 | 9 / 6 | |
| 0.0.10 | 9 / 6 | |
| 0.0.7 | 9 / 6 | |
| 0.0.6 | 8 / 6 | |
| 0.0.3 | 8 / 6 |
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.