first-event
Race event-emitter events, resolves the first to occur. Promise-based ee-first
first-event@1.0.0 was published on 2016-01-28. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All first-event versions · Permanent reference to 1.0.0 · View npm registry JSON
Package specifications
| Version | 1.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2016-01-28T07:17:16.761Z |
| Node.js requirement | Not declared |
| 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 | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 12 |
| Repository stars | 1 |
| Repository forks | 1 |
Install first-event 1.0.0
npm install first-event@1.0.0 pnpm add first-event@1.0.0 yarn add first-event@1.0.0
Runtime dependencies
- 101 ^1.2.0
- assert-args ^1.0.3
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.
- 101@1.6.3 — direct
- assert-args@1.2.1 — direct
- clone@1.0.4 — indirect
- compound-subject@0.0.1 — indirect
- debug@2.6.9 — indirect
- deep-eql@0.1.3 — indirect
- get-prototype-of@0.0.0 — indirect
- is-capitalized@1.0.0 — indirect
- is-class@0.0.4 — indirect
- keypather@1.10.2 — indirect
- ms@2.0.0 — indirect
- type-detect@0.1.1 — indirect
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-Review | 1/10 — Found 1/7 approved changesets -- score normalized to 1 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| 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
- Readable npm registry JSON — retrieved 2026-11-04T16:22:38.755Z
- https://api.deps.dev/v3/systems/npm/packages/first-event/versions/1.0.0 — retrieved 2026-11-04T16:22:39.003Z
- https://api.deps.dev/v3/systems/npm/packages/first-event/versions/1.0.0:dependencies — retrieved 2026-11-04T16:22:39.085Z
- https://api.deps.dev/v3/projects/github.com%2Ftjmehta%2Ffirst-event — retrieved 2026-11-04T16:22:39.257Z