domma-js@0.44.0
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection confirms a postinstall-triggered, first-party AI assistance setup that can alter project-level assistant configuration, with a prompt whose blank response accepts. The behavior is guarded and package-aligned, so it warrants a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package in a non-CI node_modules context and accepting, or leaving blank, the install prompt.
Impact
The package can introduce project-level AI guidance and settings that may affect later AI assistant behavior.
Mechanism
The hook copies CLAUDE.md and .claude/ plus related assistance files into the project root when those destinations do not already exist.
AI rationale
Source inspection confirms a postinstall-triggered, first-party AI assistance setup that can alter project-level assistant configuration, with a prompt whose blank response accepts. The behavior is guarded and package-aligned, so it warrants a warning rather than a block.
Evidence
package.jsonbin/postinstall.jsCLAUDE.md.claude/blueprints/types/
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs bin/postinstall.js after installation.
- The install hook can copy package-provided AI assistance files into the consumer project, including CLAUDE.md and .claude/.
- The hook is gated by an interactive prompt, but blank input accepts the default yes response.
- The CLI also exposes an explicit setup-ai command that prompts before copying the same files.
- The flagged view template is a generated view skeleton with a template URL and lifecycle methods.
Evidence against
- The install hook skips development and CI contexts and checks that it is running from node_modules.
- The install prompt permits declining, and copies only when destination files or directories do not already exist.
- The CLI setup command asks for confirmation before copying files.
- Inspected source shows no network endpoint or credential forwarding in the reviewed behavior.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
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.44.0.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.44.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.