log-process-errors
1
Versions
—
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
ehmicky
Keywords
code-qualitydebuggingerrorerror-handlererror-handlingexceptionhandlerhandlingjavascriptlibraryloggingmonitoringnodejsprocesspromisetesttestingtypescriptuncaughtuncaught-exceptions
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:is-plain-obj | AI (phantom-deps): ESM package; phantom-dep heuristic misfires on config-file references in built output. | ai | |
| phantom-deps | phantom-dep:is-error-instance | AI (phantom-deps): Same publisher's dep; config-file reference pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:set-error-message | AI (phantom-deps): Same publisher's dep; config-file reference pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:normalize-exception | AI (phantom-deps): Same publisher's dep; config-file reference pattern, not a real phantom dep. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 12.0.1 | 4 / 8 |
v12.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.