@types/relateurl
TypeScript definitions for relateurl
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://github.com/tkrotoff | AI (email-domain): The 'email' field is actually a GitHub profile URL used in the author field (Name <URL> format), not an email address. No real domain hijacking risk exists. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.2.33 | 0 / 0 | |
| 0.2.32 | 0 / 0 | |
| 0.2.31 | 0 / 0 | |
| 0.2.30 | 0 / 0 | |
| 0.2.29 | 0 / 0 | |
| 0.2.28 | 0 / 0 | |
| 0.2.27 | 0 / 0 |
v0.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
2 findingsMaintainer email 'https://github.com/tkrotoff' uses domain 'https://github.com/tkrotoff' 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.