require-relative
require and resolve modules relative to a path of your choice
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
kamicane
Keywords
requireresolvemodulesrelative
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:kamicane | AI (email-domain): Author field uses '@kamicane' as a social handle, not a real email domain. Package is 12+ years old with 1 version; no real hijack vector here. | ai | |
| provenance | no-provenance | AI (provenance): Expected for a 12-year-old single-version package. Common across npm ecosystem. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.8.7 | 0 / 0 |
v0.8.7
2 findings
HIGH
Unclaimed maintainer email domain: kamicane
email-domain
Maintainer email '@kamicane' uses domain 'kamicane' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
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.