@jitl/quickjs-wasmfile-debug-asyncify

Variant of quickjs library: Variant with separate .WASM file. Supports browser ESM, NodeJS ESM, and NodeJS CommonJS.

@jitl/quickjs-wasmfile-debug-asyncify@0.32.0 was published on 2026-02-16. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @jitl/quickjs-wasmfile-debug-asyncify versions · Permanent reference to 0.32.0

Package specifications

Version0.32.0
License declarationMIT
Published2026-02-16T04:48:51.528Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size1893.32 KiB
Published file count24
Package typeNot declared
ES module entry./dist/index.mjs
Default entry./dist/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies1
Repository stars1732
Repository forks140

Install @jitl/quickjs-wasmfile-debug-asyncify 0.32.0

npm install @jitl/quickjs-wasmfile-debug-asyncify@0.32.0
pnpm add @jitl/quickjs-wasmfile-debug-asyncify@0.32.0
yarn add @jitl/quickjs-wasmfile-debug-asyncify@0.32.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review1/10 — Found 3/20 approved changesets -- score normalized to 1
Maintained1/10 — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Security-Policy0/10 — security policy file not detected
License9/10 — license file detected
Fuzzing10/10 — project is fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness