← Home

@playcraft/build

npm

PlayCraft 构建系统核心包，提供 Playable Ads 的构建、打包和优化功能。

13
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

homkeraix-playablechenweifang

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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
typosquat typosquat.levenshtein:esbuild AI (typosquat): Scoped package @playcraft/build; Levenshtein match to esbuild 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

Versions (showing 13 of 13)

Version Deps Published
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.15 17 / 5
0.0.13 16 / 4
0.0.11 16 / 4
0.0.10 16 / 4
0.0.4 16 / 4
0.0.3 16 / 4
0.0.2 15 / 4

v0.0.44

1 finding
LOW No provenance attestation provenance

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

v0.0.43

1 finding
LOW No provenance attestation provenance

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

v0.0.42

1 finding
LOW No provenance attestation provenance

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

v0.0.41

1 finding
LOW No provenance attestation provenance

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

v0.0.40

1 finding
LOW No provenance attestation provenance

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

v0.0.15

1 finding
LOW No provenance attestation provenance

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

v0.0.13

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.0.11

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.0.10

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.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

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.0.2

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.