domma-js@0.51.12
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe postinstall hook installs package-owned Claude Code context files unless the user declines, and the CLI provides a prompted setup path. This warrants a warning for guarded agent configuration setup, but the inspected source does not establish malicious behavior or an unconsented broad control-surface mutation.
Decision evidence
public snapshot- package.json runs bin/postinstall.js as an npm postinstall hook.
- The hook prompts before copying; answering no skips setup, while other answers proceed.
- When the project lacks a .claude directory, the hook recursively copies the package template into the project root.
- The CLI setup-ai command also prompts before copying assistant files and avoids replacing existing destinations.
- The inspected Claude settings contain Domma project paths and coding preferences.
- The postinstall hook skips CI environments and offers the user a chance to decline.
- The copied settings appear to provide framework guidance; the inspected excerpts show no credential transfer, remote execution, or permission changes.
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.51.12.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.51.12 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.