@playcraft/build
PlayCraft 构建系统核心包,提供 Playable Ads 的构建、打包和优化功能。
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/templates/patches/lz4.js | AI (source-diff): Bundled third-party lz4js browserify build shipped as template asset, not injected obfuscated code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): javascript-obfuscator is a legitimate build feature for this build-tooling package. | ai | |
| source-diff | net-exec-file:dist/templates/playcanvas-stable.min.js | AI (source-diff): Official PlayCanvas engine minified bundle used as project template, matches package purpose. | ai | |
| phantom-deps | phantom-dep:terser | AI (phantom-deps): terser is a declared peer/optional dep used via vite config; not directly imported in source is expected for build tool configs. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @playcraft/build; Levenshtein match to uuid is a false positive for this namespace. | ai | |
| phantom-deps | phantom-dep:lightningcss | AI (phantom-deps): lightningcss is a declared runtime dep used in config files; stable false positive for this build tool package. | ai | |
| typosquat | typosquat.levenshtein:esbuild | AI (typosquat): Scoped package @playcraft/build; Levenshtein match to esbuild is a false positive for this namespace. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.0.52 | 19 / 5 | |
| 0.0.51 | 19 / 5 | |
| 0.0.50 | 19 / 5 | |
| 0.0.49 | 18 / 6 | |
| 0.0.48 | 18 / 6 | |
| 0.0.47 | 18 / 6 | |
| 0.0.46 | 18 / 6 | |
| 0.0.45 | 18 / 6 | |
| 0.0.44 | 18 / 6 | |
| 0.0.43 | 18 / 6 | |
| 0.0.42 | 18 / 6 | |
| 0.0.41 | 18 / 6 | |
| 0.0.40 | 18 / 6 | |
| 0.0.39 | 18 / 6 | |
| 0.0.38 | 18 / 6 | |
| 0.0.37 | 18 / 6 | |
| 0.0.36 | 18 / 6 | |
| 0.0.35 | 18 / 6 | |
| 0.0.34 | 18 / 6 | |
| 0.0.33 | 18 / 6 | |
| 0.0.32 | 18 / 6 | |
| 0.0.31 | 18 / 6 | |
| 0.0.29 | 18 / 6 | |
| 0.0.28 | 18 / 6 | |
| 0.0.27 | 18 / 6 | |
| 0.0.26 | 18 / 6 | |
| 0.0.25 | 18 / 6 | |
| 0.0.24 | 18 / 6 | |
| 0.0.23 | 17 / 5 | |
| 0.0.21 | 17 / 5 | |
| 0.0.19 | 17 / 5 | |
| 0.0.17 | 17 / 5 | |
| 0.0.15 | 17 / 5 | |
| 0.0.14 | 17 / 5 | |
| 0.0.13 | 16 / 4 | |
| 0.0.11 | 16 / 4 | |
| 0.0.10 | 16 / 4 | |
| 0.0.9 | 16 / 4 | |
| 0.0.8 | 16 / 4 | |
| 0.0.4 | 16 / 4 | |
| 0.0.3 | 16 / 4 | |
| 0.0.2 | 15 / 4 |
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
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.23
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.19
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package 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.14
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.