domma-js@0.51.6
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe install-time hook can add first-party agent configuration files to a consumer project, and an empty prompt response proceeds, so this warrants a warning under the agent integration policy. The inspected code provides no evidence of exfiltration, destructive behavior, or remote payload execution.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
npm installation in a detected project context, followed by an empty or affirmative response to the prompt.
Impact
Adds package-provided agent guidance and settings to the project; inspected code does not establish credential exposure or remote control.
Mechanism
The hook copies CLAUDE.md, .claude, blueprints, and types from package templates into the project root when destinations are absent.
AI rationale
The install-time hook can add first-party agent configuration files to a consumer project, and an empty prompt response proceeds, so this warrants a warning under the agent integration policy. The inspected code provides no evidence of exfiltration, destructive behavior, or remote payload execution.
Evidence
package.jsonbin/postinstall.jsCLAUDE.md.claude/blueprints/types/
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs bin/postinstall.js during installation.
- The postinstall hook offers Claude Code files for copying into the consumer project and waits for a prompt; entering “n” cancels, while an empty response proceeds.
- The postinstall hook copies the package’s .claude directory and other setup files into the project when destinations do not already exist.
- The explicit setup-ai CLI also prompts before copying files and skips destinations that already exist.
- The template view contains ordinary view lifecycle hooks and a commented example request.
Evidence against
- The hook checks its installation context and returns if it cannot find a project root or the templates.
- The inspected setup code copies package-owned files and shows no network or credential operation.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinified
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node bin/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node bin/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpublic/dist/domma.esm.jsView file
9patternName = generic_password
severity = medium
line = 9
Medium
bin/postinstall.js
Findings
1 Critical3 High6 Medium4 Low
CriticalAi Agent Control Hijackbin/postinstall.js
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedtemplates/view-template/view.js
HighKnown Malware Source Similaritybin/domma-cli.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumSecret Patternpublic/dist/domma.esm.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSecret Patternpublic/dist/domma.min.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to domma-js@0.51.6.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.51.6 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.