@kdrrr/overcast
overcast — senses (video/audio/image) + OSINT reach for any agent, built on pi
This report shows the evidence for @kdrrr/overcast@0.0.6. 1 of 6 known versions is blocked or flagged. The newest version, 0.0.15, is flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe package has substantial benign, user-invoked media/OSINT functionality, but the postinstall script performs a concrete unconsented mutation of an AI-agent dependency config file. That meets the firewall boundary for blocking lifecycle AI-agent control-surface mutation despite no credential or network abuse. Product guard normalized a concrete AI-agent control hijack publish_block to the blockable dangerous-capability shape.
Decision evidence
public snapshot- package.json defines postinstall: node scripts/brand-pi.mjs
- scripts/brand-pi.mjs walks node_modules and writes @earendil-works/pi-coding-agent/package.json
- postinstall changes piConfig.name for an AI coding agent dependency without user command
- dist/bin/overcast.js runtime also writes ~/.pi/agent/settings.json quietStartup when launched
- No install-time network, credential harvesting, or exfiltration found
- Network/curl usage is in user-invoked OSINT/media providers and examples
- Shell/child_process execution is tied to CLI provider commands after user invocation
- skills install writes ~/.claude/skills only via explicit overcast skills install command
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
dist/extension/overcast.jsView on unpkg · L110Findings
Affected versions and remediation
This report applies to @kdrrr/overcast@0.0.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing @kdrrr/overcast@0.0.6. 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.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.