@dabh/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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:fix-esm | AI (dependencies): fix-esm is a legitimate ESM/CJS interop utility; its use in a diagnostics package is appropriate and consistent with the package's purpose. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread Sigstore provenance adoption; no provenance is expected and consistent across all versions of this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.0.8 | 3 / 10 | |
| 2.0.7 | 4 / 10 | |
| 2.0.6 | 4 / 10 | |
| 2.0.5 | 3 / 10 | |
| 2.0.3 | 3 / 10 | |
| 2.0.2 | 3 / 10 |
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.