Runtime and polyfill for wasm targets
88%
Total Score
healthy
Healthy: active releases and an organization-backed repository outweigh workflow pinning and package-linkage cautions.
The repository name does not match the package and its README does not mention @napi-rs/wasm-runtime. Although a name mismatch is normal for a monorepo, the absence of both signals creates a package-to-repository mapping concern.
The project uses TypeScript, npm scripts, and esbuild, and has a build tool. No security scanning tools were detected, which is a modest hygiene gap, but other repository controls provide some compensation.
All seven workflows were analyzed with no untrusted checkout or script-injection findings. However, 132 of 135 action uses are unpinned, and a high-confidence low-severity finding reports an ad hoc package installation; these weaken workflow reproducibility and hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@tybys/wasm-util Version ^0.10.3 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.