domma-js@0.50.3
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe install hook can write package-owned assistant configuration into a consumer project, and its prompt defaults to proceeding, leaving meaningful consent risk. The prompt and destination checks make this a warning-level agent extension lifecycle risk rather than a confirmed attack.
Decision evidence
public snapshot- package.json runs bin/postinstall.js during installation.
- The postinstall hook runs in eligible node_modules installs and skips development and CI contexts.
- The hook asks whether to copy AI assistance files; only an explicit “n” or “no” declines, so an empty response proceeds.
- The hook copies package-provided files into the consumer project, including CLAUDE.md and .claude/.
- The CLI also offers an interactive setup command that copies AI assistance files into the current project.
- The indicated view template contains ordinary view lifecycle examples, not install-time behavior.
- The postinstall hook checks its install context and requires an interactive prompt before copying files.
- Copies are limited to files and directories that do not already exist; inspected sources show no network transmission or credential handling.
Source & flagged code
7 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.50.3.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.50.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.