@hapi/teamwork
Wait for multiple callback
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): cjihrig and marsup are well-known hapi/Node.js contributors; legitimate maintainer update. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): hueniverse (Eran Hammer) has been transitioning hapi maintenance; removal is expected. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Small stable utility in hapi ecosystem; dormancy is normal, and content is unchanged. | ai | |
| provenance | publisher-changed | AI (provenance): devinivy is a long-standing, highly trusted hapi ecosystem maintainer; this transition is consistent with known hapi.js project governance. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 0 / 5 | |
| 6.0.0 | 0 / 5 | |
| 5.1.1 | 0 / 4 | |
| 5.1.0 | 0 / 2 | |
| 5.0.0 | 0 / 2 | |
| 4.0.0 | 0 / 2 | |
| 3.3.1 | 0 / 2 | |
| 3.3.0 | 0 / 3 |
v6.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-08-21. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-05-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-13. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.