deasync 0.1.27
Turns async function into sync via JavaScript wrapper of Node event loop
deasync@0.1.27 was published on 2022-07-06. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.11.0.
All deasync versions · Permanent reference to 0.1.27 · Latest release
Package specifications
| Version | 0.1.27 |
|---|---|
| License declaration | MIT |
| Published | 2022-07-06T14:16:28.723Z |
| Node.js requirement | >=0.11.0 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 6173.74 KiB |
| Published file count | 95 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 1005 |
| Repository forks | 74 |
Install deasync 0.1.27
npm install deasync@0.1.27 pnpm add deasync@0.1.27 yarn add deasync@0.1.27
Runtime dependencies
- bindings ^1.5.0
- node-addon-api ^1.7.1
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.
- bindings@1.5.0 — direct
- file-uri-to-path@1.0.0 — indirect
- node-addon-api@1.7.2 — direct
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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Code-Review | 2/10 — Found 7/27 approved changesets -- score normalized to 2 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/deasync/0.1.27 — retrieved 2026-10-29T10:53:35.374Z
- https://api.deps.dev/v3/projects/github.com%2Fabbr%2Fdeasync — retrieved 2026-10-29T10:05:56.468Z
- https://api.deps.dev/v3/systems/npm/packages/deasync/versions/0.1.27 — retrieved 2026-10-29T10:53:35.884Z
- https://api.deps.dev/v3/systems/npm/packages/deasync/versions/0.1.27:dependencies — retrieved 2026-10-29T10:53:35.911Z