p5
1
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
p5.jsstalgiagoutofambitlimzykennethksen0lmccartdavepagurekqianqianye
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): p5 is the canonical p5.js library, not a typosquat of pg; name collision is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): p5 is the canonical p5.js library, not a typosquat of qs; name collision is coincidental. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a WebGPU swizzle proxy — standard JS Proxy pattern, not obfuscation. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.2.3 | 13 / 30 |
v2.2.3
2 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'pg'
typosquat
Package name 'p5' 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.