cloud-pc-templates-marketplace@1.2.1
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo automatic npm lifecycle attack or covert data theft was found. The package nevertheless ships a deployment path that activates powerful, insufficiently constrained agent services, so it warrants a warning for dangerous capability.
Decision evidence
public snapshot- The marketplace end script clones the repository, starts every JavaScript agent, and installs and starts nested archive packages.
- The Node connector accepts package names and runs npm install in tracked projects.
- The Angular connector overwrites route files and recursively deletes an existing components directory.
- The vector server pulls a model and clones or updates a mutable repository at runtime.
- A nested Playwright package has a postinstall hook, but it runs only after the marketplace setup extracts and installs it.
- The root manifest has no preinstall, install, or postinstall hook.
- The declared root entry point, index.js, is absent, so ordinary package import cannot start these tools.
- The risky servers and setup scripts require explicit execution or the separate marketplace end script; no secret harvesting or covert exfiltration was found.
Source & flagged code
7 flaggedPackage source references child process execution.
misc/vectorDb/vectorDbServer.jsView on unpkg · L6A single source file combines environment access, network access, and code or shell execution; review context before blocking.
misc/vectorDb/vectorDbServer.jsView on unpkg · L184Findings
Affected versions and remediation
This report applies to cloud-pc-templates-marketplace@1.2.1.
See all versions of cloud-pc-templates-marketplace for other recorded verdicts.
- Review the evidence and your use of cloud-pc-templates-marketplace@1.2.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.