← Home

topo

npm Repository Homepage

Topological sorting with grouping support

13
Versions
BSD-3-Clause
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

devinivyhueniversemarsupnlfwyatt

Keywords

topologicalsorttoposorttopsort

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Added maintainers (wyatt, marsup, nlf) are established hapi.js core team members. ai
provenance publisher-changed AI (provenance): Publisher change from devinivy to hueniverse (Eran Hammer) is a known hapi.js ecosystem maintainer consolidation. ai

Versions (showing 13 of 13)

Version Deps Published
3.0.3 1 / 2
3.0.2 1 / 2
3.0.1 1 / 2
3.0.0 1 / 2
2.1.1 1 / 2
2.0.2 1 / 2
2.0.1 1 / 2
2.0.0 1 / 2
1.1.0 1 / 2
1.0.3 1 / 2
1.0.2 1 / 1
1.0.1 1 / 1
1.0.0 1 / 1

v3.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

2 findings
HIGH Publisher changed: devinivy → hueniverse (on 2018-10-31) provenance

This version was published by a different npm account than previous versions on 2018-10-31. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

2 findings
HIGH Publisher changed: devinivy → hueniverse (on 2017-09-26) provenance

This version was published by a different npm account than previous versions on 2017-09-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: hueniverse → nargonath (on 2024-01-01) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-01-01. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: hueniverse → devinivy (on 2016-07-17) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-07-17. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: devinivy → hueniverse (on 2015-11-01) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-11-01. This could indicate a legitimate maintainer transition or an account compromise.