tap 0.0.7

A Test-Anything-Protocol library

tap@0.0.7 was published on 2011-12-07. Its manifest declares 10 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is *.

Deprecated: Versions of tap before v18 are no longer maintained. Please upgrade.

All tap versions · Permanent reference to 0.0.7 · View npm registry JSON · Latest release

Package specifications

Version0.0.7
License declarationNot declared
Published2011-12-07T00:43:11.747Z
Node.js requirement*
Type declarationsNot declared
Runtime dependency count10
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylib/main.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies11
Repository stars2426
Repository forks283

Install tap 0.0.7

npm install tap@0.0.7
pnpm add tap@0.0.7
yarn add tap@0.0.7

Runtime dependencies

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.

  • slide@1.1.6 — indirect
  • tap-runner@0.0.7 — direct
  • inherits@1.0.0 bundled — direct
  • tap-assert@0.0.7 bundled — direct
  • tap-consumer@0.0.1 bundled — direct
  • tap-global-harness@0.0.1 bundled — direct
  • tap-harness@0.0.3 bundled — direct
  • tap-producer@0.0.1 bundled — direct
  • tap-results@0.0.2 bundled — direct
  • tap-test@0.0.2 bundled — direct
  • yamlish@0.0.1 bundled — 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.

Evidence and freshness