ambi 3.1.1
Execute a function ambidextrously (normalizes the differences between synchronous and asynchronous functions). Useful for treating synchronous functions as asynchronous functions (like supporting both synchronous and asynchronous event definitions automat
ambi@3.1.1 was published on 2018-09-03. 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.8.
All ambi versions · Permanent reference to 3.1.1 · Latest release
Package specifications
| Version | 3.1.1 |
|---|---|
| License declaration | MIT |
| Published | 2018-09-03T11:56:10.023Z |
| Node.js requirement | >=0.8 |
| 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 | 30.09 KiB |
| Published file count | 8 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | 17 |
| Repository forks | 3 |
Install ambi 3.1.1
npm install ambi@3.1.1 pnpm add ambi@3.1.1 yarn add ambi@3.1.1
Runtime dependencies
- editions ^2.0.2
- typechecker ^4.3.0
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.
- editions@2.3.1 — direct
- errlop@2.2.0 — indirect
- semver@6.3.1 — indirect
- typechecker@4.11.0 — 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.
| Maintained | 10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Security-Policy | 10/10 — security policy file detected |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 10/10 — SAST tool is run on all commits |
Evidence and freshness
- https://registry.npmjs.org/ambi/3.1.1 — retrieved 2026-10-30T02:45:56.968Z
- https://api.deps.dev/v3/projects/github.com%2Fbevry%2Fambi — retrieved 2026-10-30T02:45:51.268Z
- https://api.deps.dev/v3/systems/npm/packages/ambi/versions/3.1.1 — retrieved 2026-10-30T02:45:57.527Z
- https://api.deps.dev/v3/systems/npm/packages/ambi/versions/3.1.1:dependencies — retrieved 2026-10-30T02:45:57.536Z