teamwork 3.2.0

Wait for multiple callback

teamwork@3.2.0 was published on 2019-03-26. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: This module has moved and is now available at @hapi/teamwork. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.

All teamwork versions · Permanent reference to 3.2.0 · Latest release

Package specifications

Version3.2.0
License declarationBSD-3-Clause
Published2019-03-26T18:01:02.308Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4.63 KiB
Published file count6
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars14
Repository forks14

Install teamwork 3.2.0

npm install teamwork@3.2.0
pnpm add teamwork@3.2.0
yarn add teamwork@3.2.0

Runtime dependencies

  • None declared

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.

    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.

    Maintained4/10 — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
    Code-Review3/10 — Found 9/26 approved changesets -- score normalized to 3
    Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
    Binary-Artifacts10/10 — no binaries found in the repo
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Fuzzing0/10 — project is not fuzzed
    License9/10 — license file detected
    Branch-Protection0/10 — branch protection not enabled on development/release branches
    Security-Policy10/10 — security policy file detected
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness