@unrs/resolver-binding-wasm32-wasi
UnRS Resolver Node API
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): The .wasm is the package's declared deliverable (WASM resolver binding). | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Fetch is used to load the WASM binary in the browser entry point — canonical pattern for WASM packages. | ai | |
| phantom-deps | phantom-dep:@emnapi/core | AI (phantom-deps): WASM/emnapi deps are referenced by build tooling, not direct JS imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emnapi/runtime | AI (phantom-deps): Same as @emnapi/core — build-time WASM runtime dep, not directly imported in JS. | ai | |
| bogus-package | bogus-package | AI (bogus-package): WASM binding packages typically have minimal READMEs and no keywords; not indicative of spam. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.12.2 | 3 / 0 | |
| 1.12.1 | 3 / 0 | |
| 1.12.0 | 3 / 0 | |
| 1.11.1 | 1 / 0 | |
| 1.11.0 | 1 / 0 | |
| 1.10.1 | 1 / 0 | |
| 1.10.0 | 1 / 0 | |
| 1.9.2 | 1 / 0 | |
| 1.9.1 | 1 / 0 | |
| 1.9.0 | 1 / 0 | |
| 1.8.1 | 1 / 0 | |
| 1.8.0 | 1 / 0 | |
| 1.7.13 | 1 / 0 | |
| 1.7.12 | 1 / 0 | |
| 1.7.11 | 1 / 0 | |
| 1.7.10 | 1 / 0 | |
| 1.7.9 | 1 / 0 | |
| 1.7.8 | 1 / 0 | |
| 1.7.7 | 1 / 0 | |
| 1.7.6 | 1 / 0 | |
| 1.7.5 | 1 / 0 | |
| 1.7.4 | 1 / 0 | |
| 1.7.3 | 1 / 0 | |
| 1.7.2 | 1 / 0 | |
| 1.7.1 | 1 / 0 | |
| 1.7.0 | 1 / 0 | |
| 1.6.6 | 1 / 0 | |
| 1.6.5 | 1 / 0 | |
| 1.6.4 | 1 / 0 | |
| 1.6.3 | 1 / 0 | |
| 1.6.2 | 1 / 0 | |
| 1.6.1 | 1 / 0 | |
| 1.6.0 | 1 / 0 | |
| 1.5.0 | 1 / 0 | |
| 1.4.1 | 1 / 0 | |
| 1.4.0 | 1 / 0 | |
| 1.3.3 | 1 / 0 | |
| 1.3.2 | 1 / 0 | |
| 1.3.1 | 1 / 0 | |
| 1.3.0 | 1 / 0 |
v1.7.2
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.wasm32-wasi.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.