pit-js@5.1.1
Pollable Input
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe preinstall script mutates Git configuration and can disrupt the enclosing repository's hooks. This presents a concrete install-time risk, though the package's runtime code appears aligned with an input library and the source does not establish malicious intent.
Decision evidence
public snapshot- The automatic preinstall runs a command that sets Git's hooks path to `git_hooks`.
- The package file allowlist omits `git_hooks`, so the configured directory is not included in the published package.
- The runtime entrypoint exports input and vector helpers, consistent with the stated input library.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThe automatic preinstall runs a command that sets Git's hooks path to `git_hooks`.
package.jsonView on unpkg · L19Findings
Affected versions and remediation
This report applies to pit-js@5.1.1.
See all versions of pit-js for other recorded verdicts.
- Review the evidence and your use of pit-js@5.1.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.