← Home

pn

npm Repository Homepage

Promisify the node standard library.

4
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

cscott

Keywords

promisenode

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:pg AI (typosquat): 'pn' (promise+node) is a legitimate 2-letter name with 2M weekly downloads; not a typosquat of 'pg'. ai
typosquat typosquat.levenshtein:qs AI (typosquat): 'pn' is a legitimate 2-letter package; edit distance to 'qs' is coincidental. ai
typosquat typosquat.levenshtein:pino AI (typosquat): 'pn' is a legitimate 2-letter package; edit distance to 'pino' is coincidental. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Package is 11+ years old with 2M weekly downloads; 0.0.0 is its legitimate initial version. ai
semgrep semgrep:child-process-import AI (semgrep): pn is a promisification wrapper for Node stdlib including child_process; importing child_process is the package's core purpose, not a risk. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is in scripts/generate.js (a codegen build script), used to introspect Node built-ins for auto-generating promise wrappers. Not runtime risk. ai

Versions (showing 4 of 4)

Version Deps Published
1.1.0 0 / 3
1.0.0 0 / 3
0.0.1 0 / 2
0.0.0 0 / 0

v1.1.0

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

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name 'pn' is 1 edit(s) away from popular package 'pg'.

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.