diagnostics
Tools for debugging your node.js modules and event loop
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 14 years old by a known Node.js ecosystem author; 0.0.0 is the legitimate initial release, not a malicious throwaway version. | ai | |
| dependencies | unvetted-dep:kuler | AI (dependencies): kuler is a small color utility by the same author (3rd-Eden); its use is expected and consistent with this diagnostics/debug library's purpose. | ai | |
| dependencies | unvetted-dep:enabled | AI (dependencies): enabled is a feature-flag utility by the same author (3rd-Eden); its use is expected in this diagnostics library. | ai | |
| dependencies | unvetted-dep:colorspace | AI (dependencies): colorspace is a color conversion utility by the same author (3rd-Eden); its use is expected for color-aware debug output in this library. | ai | |
| dependencies | unvetted-dep:storage-engine | AI (dependencies): storage-engine is pinned to 3.0.x in a mature, long-established package; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package by known maintainer; lack of provenance is common and not a meaningful risk signal here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 3 / 10 | |
| 2.0.2 | 4 / 11 | |
| 2.0.1 | 4 / 11 | |
| 2.0.0 | 4 / 11 | |
| 1.1.1 | 3 / 3 | |
| 1.0.1 | 3 / 3 | |
| 1.0.0 | 3 / 3 | |
| 0.0.4 | 5 / 3 | |
| 0.0.3 | 5 / 3 | |
| 0.0.2 | 6 / 3 | |
| 0.0.1 | 5 / 3 | |
| 0.0.0 | 0 / 2 |
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.