tap-only 0.0.1
My fabulous module
tap-only@0.0.1 was published on 2015-11-17. Its manifest declares 1 runtime dependency and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.
All tap-only versions · Permanent reference to 0.0.1 · Latest release
Package specifications
| Version | 0.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2015-11-17T12:56:55.656Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 1 |
| 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 | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 9 |
| Repository stars | 1 |
| Repository forks | 0 |
Install tap-only 0.0.1
npm install tap-only@0.0.1 pnpm add tap-only@0.0.1 yarn add tap-only@0.0.1
Runtime dependencies
- fallback-cli ^2.0.2
Peer requirements
- tap *
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- caller@1.1.0 — indirect
- es-errors@1.3.0 — indirect
- fallback-cli@2.0.2 — direct
- function-bind@1.1.2 — indirect
- hasown@2.0.4 — indirect
- is-core-module@2.17.0 — indirect
- path-parse@1.0.7 — indirect
- resolve@1.22.13 — indirect
- supports-preserve-symlinks-flag@1.0.0 — 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 | 0/10 — Found 0/10 approved changesets -- score normalized to 0 |
|---|---|
| SAST | 0/10 — no SAST tool detected |
| 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 |
| 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 |
Evidence and freshness
- https://registry.npmjs.org/tap-only/0.0.1 — retrieved 2026-10-30T17:29:11.537Z
- https://api.deps.dev/v3/systems/npm/packages/tap-only/versions/0.0.1 — retrieved 2026-10-30T17:29:12.043Z
- https://api.deps.dev/v3/systems/npm/packages/tap-only/versions/0.0.1:dependencies — retrieved 2026-10-30T17:29:12.085Z
- https://api.deps.dev/v3/projects/github.com%2Fjamestalmage%2Ftap-only — retrieved 2026-10-30T17:29:12.527Z