← Home

@qnx/errors

npm Repository Homepage
7
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

yatendra121kushwaha

Keywords

errorserror codes

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
email-domain unclaimed-email:https://github.com/yatendra121 AI (email-domain): Maintainer 'email' is a GitHub profile URL, not an email address; domain check is a parser false positive stable across all versions. ai

Versions (showing 7 of 7)

Version Deps Published
0.8.7 0 / 0
0.8.0 0 / 0
0.7.13 0 / 0
0.7.12 0 / 0
0.7.10 0 / 0
0.7.9 0 / 0
0.7.8 0 / 0

v0.8.7

2 findings
HIGH Unclaimed maintainer email domain: https://github.com/yatendra121 email-domain

Maintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' 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.

v0.8.0

2 findings
HIGH Unclaimed maintainer email domain: https://github.com/yatendra121 email-domain

Maintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' 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.

v0.7.13

2 findings
HIGH Unclaimed maintainer email domain: https://github.com/yatendra121 email-domain

Maintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' 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.

v0.7.12

2 findings
HIGH Unclaimed maintainer email domain: https://github.com/yatendra121 email-domain

Maintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' 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.

v0.7.10

2 findings
HIGH Unclaimed maintainer email domain: https://github.com/yatendra121 email-domain

Maintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' 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.

v0.7.9

2 findings
HIGH Unclaimed maintainer email domain: https://github.com/yatendra121 email-domain

Maintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' 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.

v0.7.8

2 findings
HIGH Unclaimed maintainer email domain: https://github.com/yatendra121 email-domain

Maintainer email 'https://github.com/yatendra121' uses domain 'https://github.com/yatendra121' 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.