good
Server and process monitoring plugin
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): Publisher change from arb to marsup occurred in March 2018 — a long-settled transition within the hapijs org. marsup is a highly trusted publisher with a strong track record. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is the intentional plugin/reporter loading mechanism for this monitoring framework; it loads user-configured modules by name, not attacker-controlled input. | ai |
Versions (showing 92 of 92)
| Version | Deps | Published |
|---|---|---|
| 8.1.2 | 4 / 4 | |
| 8.1.1 | 4 / 4 | |
| 8.1.0 | 4 / 4 | |
| 8.0.1 | 4 / 4 | |
| 8.0.0 | 4 / 4 | |
| 7.3.0 | 4 / 5 | |
| 7.2.0 | 4 / 5 | |
| 7.1.0 | 4 / 5 | |
| 7.0.2 | 4 / 4 | |
| 7.0.1 | 4 / 4 | |
| 7.0.0 | 4 / 4 | |
| 6.6.3 | 5 / 3 | |
| 6.6.2 | 5 / 3 | |
| 6.6.1 | 5 / 3 | |
| 6.6.0 | 5 / 3 | |
| 6.5.0 | 5 / 3 | |
| 6.4.0 | 5 / 3 | |
| 6.3.0 | 5 / 3 | |
| 6.2.0 | 5 / 3 | |
| 6.1.4 | 5 / 3 | |
| 6.1.3 | 5 / 3 | |
| 6.1.2 | 5 / 3 | |
| 6.1.1 | 5 / 3 | |
| 6.1.0 | 5 / 3 | |
| 6.0.0 | 4 / 3 | |
| 5.1.2 | 4 / 3 | |
| 5.1.1 | 4 / 3 | |
| 5.1.0 | 5 / 3 | |
| 5.0.0 | 5 / 3 | |
| 4.0.2 | 6 / 3 | |
| 4.0.1 | 6 / 3 | |
| 4.0.0 | 6 / 2 | |
| 3.1.1 | 7 / 2 | |
| 3.1.0 | 7 / 2 | |
| 3.0.1 | 7 / 3 | |
| 2.5.1 | 6 / 3 | |
| 2.5.0 | 6 / 3 | |
| 2.4.2 | 6 / 3 | |
| 2.3.0 | 6 / 3 | |
| 2.2.3 | 6 / 3 | |
| 2.2.1 | 5 / 3 | |
| 2.2.0 | 5 / 3 | |
| 2.1.2 | 5 / 3 | |
| 2.1.1 | 5 / 3 | |
| 2.1.0 | 5 / 3 | |
| 2.0.0 | 5 / 3 | |
| 1.0.0 | 6 / 2 | |
| 0.12.3 | 5 / 2 | |
| 0.12.2 | 5 / 2 | |
| 0.12.1 | 5 / 2 | |
| 0.12.0 | 4 / 2 | |
| 0.11.1 | 4 / 2 | |
| 0.11.0 | 4 / 2 | |
| 0.10.0 | 4 / 2 | |
| 0.9.0 | 4 / 3 | |
| 0.8.1 | 4 / 3 | |
| 0.8.0 | 4 / 3 | |
| 0.7.0 | 4 / 3 | |
| 0.6.3 | 4 / 3 | |
| 0.6.2 | 4 / 3 | |
| 0.6.0 | 4 / 3 | |
| 0.5.16 | 4 / 3 | |
| 0.5.15 | 4 / 4 | |
| 0.5.14 | 4 / 4 | |
| 0.5.13 | 4 / 4 | |
| 0.5.12 | 4 / 4 | |
| 0.5.11 | 4 / 4 | |
| 0.5.10 | 4 / 4 | |
| 0.5.9 | 4 / 4 | |
| 0.5.8 | 4 / 4 | |
| 0.5.7 | 4 / 3 | |
| 0.5.6 | 4 / 3 | |
| 0.5.5 | 4 / 4 | |
| 0.5.4 | 4 / 4 | |
| 0.5.3 | 4 / 4 | |
| 0.5.2 | 4 / 4 | |
| 0.5.1 | 4 / 4 | |
| 0.5.0 | 4 / 4 | |
| 0.4.0 | 3 / 4 | |
| 0.3.0 | 3 / 4 | |
| 0.2.0 | 3 / 4 | |
| 0.1.8 | 3 / 4 | |
| 0.1.7 | 3 / 4 | |
| 0.1.6 | 3 / 6 | |
| 0.1.5 | 3 / 6 | |
| 0.1.4 | 3 / 6 | |
| 0.1.3 | 3 / 6 | |
| 0.1.2 | 3 / 6 | |
| 0.1.1 | 3 / 6 | |
| 0.1.0 | 3 / 6 | |
| 0.0.2 | 3 / 5 | |
| 0.0.1 | 3 / 3 |
v8.1.2
2 findingsThis version was published by a different npm account than previous versions on 2019-01-19. 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.
v8.1.1
2 findingsThis version was published by a different npm account than previous versions on 2018-03-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.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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 2016-12-01. This could indicate a legitimate maintainer transition or an account compromise.
v7.0.2
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-08-27. This could indicate a legitimate maintainer transition or an account compromise.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.