perfetto-analyzer
AI skill for Android performance analysis using Perfetto — works with Claude Code, Cursor, GitHub Copilot, Codex, Antigravity and Devin
This report shows the evidence for perfetto-analyzer@1.0.4. 4 of 4 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms unconsented postinstall mutation of broad/foreign AI-agent control surfaces, which meets the block policy even though the shipped skill content is mostly package-aligned and no exfiltration was found. The malicious verdict is based on the install-time control-surface write, not scanner labels. 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 bin/cli.js install --postinstall
- bin/cli.js postinstall path calls install(true) without prompting
- bin/cli.js copies package skill/ into six AI-agent skill directories under user home
- Targets broad/foreign agent control surfaces: .claude, .github/copilot, .cursor, .antigravity, .codex, .devin
- No network or exfiltration endpoints found in inspected source
- Skill content is aligned with Android Perfetto analysis
- Python helpers are user-invoked from the installed skill, not npm install-time
- No credential/env harvesting, eval/vm/Function, native binary loading, or remote payload fetch found
Source & flagged code
4 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 unpkgInstall-time source drops package-supplied AI-agent/MCP control files or instructions.
bin/cli.jsView on unpkg · L10Package ships non-JavaScript build or shell helper files.
skill/scripts/parse_perfetto_pb.pyView on unpkgFindings
Affected versions and remediation
This report applies to perfetto-analyzer@1.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing perfetto-analyzer@1.0.4. 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.