@types/error-stack-parser
Stub TypeScript definitions entry for error-stack-parser, which provides its own types definitions
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://www.eriwen.com | AI (email-domain): The author field contains a URL, not an email address. The analyzer is misinterpreting a URL as an email domain. No real hijack risk; publishing is controlled by the trusted 'types' npm account. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @types/* packages are intentionally tiny, dependency-free type definitions. These signals are expected and normal for all DefinitelyTyped packages. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 1 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 1.3.18 | 0 / 0 | |
| 1.3.17 | 0 / 0 |
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
2 findingsMaintainer email 'https://www.eriwen.com' uses domain 'https://www.eriwen.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.