← Home

native-promise

npm Repository Homepage

Get native `Promise` or falsey value if not available.

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

tunnckocore

Keywords

checkgetnativepromisevalidate

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Package is ~10 years old; 0.0.0 was a common early versioning convention for this publisher. No malicious indicators present. ai
email-domain unclaimed-email:tunnckocore AI (email-domain): The '@tunnckoCore' in the author field is a social handle notation, not an actual email domain. This is a stable false positive for this publisher's packages. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.1 0 / 3
1.0.0 0 / 3
0.0.0 0 / 3

v1.0.1

2 findings
HIGH Unclaimed maintainer email domain: tunnckocore email-domain

Maintainer email '@tunnckoCore' uses domain 'tunnckocore' 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. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.0

1 finding
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.