@hapi/topo
Topological sorting with grouping support
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): marsup is a core hapi.js ecosystem maintainer with a strong track record (1891 approved packages). The transition from devinivy to marsup is consistent with known hapi org consolidation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): cjihrig and marsup are established hapi.js core contributors; their addition reflects the documented hapi org maintainer consolidation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): hueniverse removal is consistent with the hapi.js org restructuring; no malicious indicators present. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is consistent with hapi ecosystem's maintenance cadence; no suspicious code changes accompany the resumed activity. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 6.0.2 | 1 / 5 | |
| 6.0.1 | 1 / 5 | |
| 6.0.0 | 1 / 5 | |
| 5.1.0 | 1 / 3 | |
| 5.0.0 | 1 / 2 | |
| 4.0.1 | 1 / 2 | |
| 4.0.0 | 1 / 2 | |
| 3.1.6 | 1 / 2 | |
| 3.1.5 | 1 / 2 | |
| 3.1.4 | 1 / 2 | |
| 3.1.3 | 1 / 2 | |
| 3.1.2 | 1 / 2 | |
| 3.1.0 | 1 / 2 |
v6.0.1
2 findingsThis version was published by a different npm account than previous versions on 2023-02-11. 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
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 2021-06-28. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.