domma-js@0.53.3
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook performs project-level AI configuration setup and treats the displayed yes-default as acceptance, leaving a lifecycle risk. Its inspected templates are package-specific guidance and preferences, so the evidence supports a warning rather than a malicious verdict.
Decision evidence
public snapshot- The manifest runs `bin/postinstall.js` during installation; the hook is limited to normal `node_modules` installs and skips CI and the package's own development tree.
- The hook asks to copy AI assistance files with a `(Y/n)` prompt and proceeds unless the answer is `n` or `no`, so accepting the displayed default copies them.
- The hook copies package-owned `CLAUDE.md` and `.claude` files into the project root only when those destinations do not already exist.
- The inspected templates provide Domma framework guidance and project preferences; the settings shown do not configure agent permissions or plugins.
- The CLI also exposes this setup through an explicit `setup-ai` command and asks whether to continue.
- The inspected setup concerns project-level files and package-specific framework guidance; it does not establish a remote channel or an active attack.
Source & flagged code
8 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 unpkgFindings
Affected versions and remediation
This report applies to domma-js@0.53.3.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.53.3 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.