serialize-error
Serialize/deserialize an error into a plain object
3
Versions
MIT
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
sindresorhus
Keywords
errorserializestringifyobjectconvertprocesssendcausedeserialize
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): sindresorhus packages consistently lack Sigstore provenance; this is a known pattern for this publisher and not a risk indicator. | ai | |
| dependencies | unvetted-dep:non-error | AI (dependencies): non-error is a sindresorhus utility package that fits the purpose of serialize-error; no malicious indicators and consistent with the package's functionality. | ai |
v13.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.