Those packages’ install-time code can run during installation under the installer’s permissions.
AI security review
scanned · by lpm-firewall-ai
This version adds manifest-level install-script approvals for other packages. Under the package firewall rules, granting that approval without the installer’s consent is dependency script approval abuse.
Static reason
One or more suspicious static signals were detected.
Trigger
A package manager that honors this `allowScripts` field installs the package and its dependencies.
Mechanism
The field approves install scripts for esbuild and @parcel/watcher without a separate user decision.
Policy narrative
The changed manifest approves install scripts for esbuild and @parcel/watcher. When installed by a package manager that honors this field, those packages can run install-time code without the installer separately approving it.
Evidence
package.json
Decision evidence
public snapshot
Evidence for block
The changed manifest declares `allowScripts` approvals for `esbuild@0.28.2` and `@parcel/watcher@2.6.0`, permitting those packages’ install scripts to run without the installing user’s approval.
Evidence against
The package describes itself as an address lookup utility, and its browser entry loads Google Maps Places for that feature.
The inspected manifest has no preinstall, install, or postinstall lifecycle hook.
The changed manifest declares allowScripts approvals for esbuild@0.28.2 and @parcel/watcher@2.6.0, permitting those packages’ install scripts to run without the installing user’s approval.
Avoid installing @ne1410s/address@0.0.221. 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.