The collector receives install and project metadata automatically; explicit opt-outs can suppress reporting.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
Source inspection confirms automatic install-time disclosure of project and installation metadata to scarf.sh, with opt-out controls but no affirmative consent requirement. This supports blocking the package for install-time data exfiltration.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installing the package with lifecycle scripts enabled runs the Scarf dependency’s postinstall hook.
Mechanism
The hook collects install and dependency details, adds the project Git revision when top-level reporting is enabled, and posts the payload to scarf.sh.
Attack narrative
Installing the package can invoke the Scarf postinstall hook. The package enables top-level reporting, and the helper defaults to reporting unless an opt-out is present. It collects install and dependency details, includes the project Git revision when applicable, and sends the payload to scarf.sh without affirmative installer consent.
package.json declares @scarf/scarf and enables its top-level install reporting; the dependency manifest runs report.js in postinstall.
report.js defaults reporting to enabled and proceeds unless an opt-out is detected; it gathers install platform, architecture, Node version, dependency details, and the project Git revision.
The install helper posts the collected payload to scarf.sh at the package-install endpoint.
The helper’s postinstall entrypoint calls the reporting function automatically.
Evidence against
The helper allows explicit opt-outs through package settings and environment variables.
The helper removes local paths and hashes some root package details before reporting.
Avoid installing @aviaviavi/org2@0.5.0. 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 ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.