node-phantom
bridge between node.js and PhantomJS
9
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
alexscheelmeyer
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used to deserialize JS functions passed over the local Node↔PhantomJS bridge protocol — core to the package's documented purpose, not an attack vector. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 is localhost; the bridge communicates with a locally spawned PhantomJS process. Benign and architecturally necessary. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used to spawn PhantomJS — the entire purpose of this package. Not a supply-chain risk. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Spawning PhantomJS is the documented core functionality of node-phantom; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by many years; absence is expected and not a risk signal here. | ai |