inert
Static file and directory handlers plugin for hapi.js
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): The hueniverse→kanongil transition is a documented, legitimate hapi.js ecosystem maintainer handoff that occurred in 2019. kanongil is a long-standing, trusted hapi.js contributor. This generalizes to all future versions of this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removals are part of the same 2019 hapi.js ecosystem consolidation under kanongil. No evidence of hostile takeover; verdict is stable for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 5.1.3 | 6 / 3 | |
| 5.1.2 | 6 / 3 | |
| 5.1.1 | 6 / 3 | |
| 5.1.0 | 6 / 3 | |
| 5.0.1 | 6 / 3 | |
| 5.0.0 | 5 / 3 | |
| 4.2.1 | 6 / 3 | |
| 4.2.0 | 6 / 3 | |
| 4.1.0 | 6 / 3 | |
| 4.0.4 | 6 / 3 | |
| 4.0.3 | 6 / 3 | |
| 4.0.2 | 6 / 3 | |
| 4.0.1 | 6 / 3 | |
| 4.0.0 | 6 / 3 | |
| 3.2.1 | 6 / 3 | |
| 3.2.0 | 6 / 5 | |
| 3.1.0 | 6 / 5 | |
| 3.0.2 | 6 / 3 | |
| 3.0.1 | 6 / 3 | |
| 3.0.0 | 6 / 3 | |
| 2.1.6 | 6 / 3 | |
| 2.1.5 | 6 / 3 | |
| 2.1.4 | 6 / 3 | |
| 2.1.3 | 6 / 3 | |
| 2.1.2 | 6 / 3 | |
| 2.1.1 | 6 / 3 | |
| 2.1.0 | 6 / 3 | |
| 2.0.0 | 5 / 3 | |
| 1.1.1 | 6 / 2 | |
| 1.1.0 | 6 / 2 | |
| 1.0.0 | 5 / 2 |
v5.1.3
2 findingsThis version was published by a different npm account than previous versions on 2019-04-02. 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.2
1 findingPackage 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 2018-11-01. 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.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 2017-11-03. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.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 2017-11-03. This could indicate a legitimate maintainer transition or an account compromise.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
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 2016-11-29. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.