← Home

yoga-wasm-web

npm Repository
17
Versions
MIT
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

quietshu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/entry.js AI (source-diff): Bundled esbuild output with readable Yoga layout classes and constants; standard build artifact. ai
source-diff source-size-tripled AI (source-diff): Size increase from adding asm.js fallback path for non-wasm environments; legitimate feature addition. ai
source-diff obfuscated-file:dist/yoga-asm.mjs AI (source-diff): Emscripten-compiled asm.js fallback for Yoga C++ engine; standard Emscripten boilerplate, not obfuscation. ai
source-diff obfuscated-file:dist/asm.js AI (source-diff): Bundled esbuild output of Yoga layout constants and API; not obfuscated malicious code. Standard for wasm/asm.js packages. ai
provenance missing-githead AI (provenance): Trusted long-standing publisher; missing gitHead reflects publish environment change, not a security concern. ai
source-diff obfuscated-file:dist/wrapAsm-57389177.js AI (source-diff): Rollup+terser bundled output of Yoga layout constants and wrappers; standard build artifact for this WASM binding package. ai
source-diff encoded-string-file:dist/asm.js AI (source-diff): Emscripten-generated ASM.js module with compiled WASM output; long encoded strings are inherent to the package's purpose. ai
source-diff obfuscated-file:dist/wrapAsm-f766f97f.js AI (source-diff): Rollup-bundled Yoga layout engine enums and WASM bindings; minified output is expected for this package's build pipeline. ai
npm-metadata no-description AI (npm-metadata): Package has been published without description across versions; not indicative of malice for this established package. ai

Versions (showing 17 of 17)

Version Deps Published
0.3.3 0 / 7
0.3.2 0 / 6
0.3.1 0 / 2
0.3.0 0 / 3
0.2.0 0 / 2
0.1.2 0 / 2
0.1.1 0 / 2
0.1.0 0 / 2
0.0.9 0 / 2
0.0.8 0 / 2
0.0.7 0 / 2
0.0.6 0 / 2
0.0.5 0 / 2
0.0.4 0 / 2
0.0.3 0 / 2
0.0.2 0 / 2
0.0.1 0 / 2

v0.3.3

4 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: quietshu.

HIGH New obfuscated file: dist/wrapAsm-f766f97f.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH Long encoded string in modified file: dist/asm.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.3.2

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: quietshu.

HIGH New obfuscated file: dist/wrapAsm-57389177.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.3.1

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[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: quietshu.

v0.3.0

5 findings
HIGH New obfuscated file: dist/asm.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/entry.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/yoga-asm.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[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: quietshu.

v0.2.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.9

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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.

v0.0.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.