modelence@0.25.0
The Node.js Framework for Real-Time MongoDB Apps
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not concrete malware, but the prepare-time repository mutation and explicit agent configuration capability are real supply-chain risks. The observed network and host metadata behavior is aligned with the framework's configured cloud runtime.
Decision evidence
public snapshot- The prepare lifecycle changes the enclosing repository's Git hooks path.
- The explicit setup command writes project configuration and Claude Code settings, and can invoke the Claude CLI.
- Runtime code sends a hostname and framework metadata to the configured Modelence service.
- There are no preinstall, install, or postinstall lifecycle hooks.
- The Git-hook action is a prepare-only Husky-style setup, not a payload chain.
- Claude configuration and cloud authentication occur through explicit CLI setup actions.
- No self-dependency, hidden downloader, credential harvesting, or arbitrary remote code execution was found.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/bin/modelence.jsView on unpkg · L1A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/bin/modelence.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to modelence@0.25.0.
See all versions of modelence for other recorded verdicts.
- Review the evidence and your use of modelence@0.25.0 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.