webmidi 3.0.0-alpha.16

WebMidi.js makes it easy to talk to MIDI instruments from a browser or from Node.js. It simplifies the control of external or virtual MIDI instruments with functions such as playNote(), setPitchBend(), sendControlChange(), etc. It also allows reacting to

webmidi@3.0.0-alpha.16 was published on 2021-09-28. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.5.

All webmidi versions · Permanent reference to 3.0.0-alpha.16 · View npm registry JSON · Latest release

Package specifications

Version3.0.0-alpha.16
License declarationMIT
Published2021-09-28T21:13:00.731Z
Node.js requirement>=8.5
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count1
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size2513.47 KiB
Published file count15
Package typeNot declared
ES module entrydist/webmidi.esm.min.js
Default entrydist/webmidi.cjs.min.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies75
Repository stars1721
Repository forks130

Install webmidi 3.0.0-alpha.16

npm install webmidi@3.0.0-alpha.16
pnpm add webmidi@3.0.0-alpha.16
yarn add webmidi@3.0.0-alpha.16

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

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.

Maintained10/10 — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
SAST10/10 — SAST tool is run on all commits

Evidence and freshness