Approved dependency code can execute during installation without the installer separately approving each dependency script.
AI security review
scanned · by lpm-firewall-ai
The manifest automatically approves install scripts for three dependencies. This is dependency script approval abuse under the package-manager approvals rule.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installing this package with a package manager that honors allowScripts.
Mechanism
The root package.json allowScripts field marks the named dependencies as approved to run install scripts.
Policy narrative
During installation, the manifest grants script approval to @google/genai@2.21.0, fsevents@2.3.3, and protobufjs@7.6.6. This matches the package-manager script approval abuse rule; no additional network behavior is needed to establish the finding.
Evidence
package.json
Decision evidence
public snapshot
Evidence for block
package.json sets allowScripts to true for @google/genai@2.21.0, fsevents@2.3.3, and protobufjs@7.6.6, granting install-script approval to dependencies.
Evidence against
The package has no preinstall, install, or postinstall lifecycle hook; its only lifecycle hook is prepublishOnly.
The approval list names specific dependency versions.
Avoid installing @harrylabsj/kiwi@0.12.7. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version's installer ran, inspect changes to package.json allowScripts and restore the approvals you explicitly reviewed. Check which dependency scripts ran; newly granted approvals do not prove immediate execution or credential theft.