cacao1
This report shows the evidence for cacao1@9.9.9, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection confirms unconsented install-time transmission of the host name to an external collection endpoint. The automatic hooks and self-dependency increase the supply-chain risk.
Decision evidence
public snapshot- Both preinstall and postinstall automatically run index.js during npm installation.
- The lifecycle code sends the installing machine's hostname to an external Pipedream endpoint.
- The package declares a runtime dependency on its own package name and compatible release range.
- The inspected source does not show file reads, credential harvesting, or destructive writes.
- The source is short and does not contain an additional downloaded payload or shell execution.
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 lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to cacao1@9.9.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing cacao1@9.9.9. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.