domma-js@0.52.2
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe postinstall hook can change project-level Claude configuration without requiring an explicit affirmative response. Its scope is limited to missing project files, and the inspected content is framework guidance, so the evidence supports a warning rather than a block.
Decision evidence
public snapshot- package.json runs bin/postinstall.js after dependency installation.
- The hook skips CI and development contexts, and proceeds only when its working directory is inside node_modules.
- The install prompt accepts any response except n or no, so an empty response continues to the copy step.
- The hook copies its bundled CLAUDE.md and .claude directory into the project only when those destinations do not already exist.
- The bundled Claude settings contain Domma-specific framework preferences and documentation paths.
- The separate setup-ai command also copies these files after asking the user whether to continue.
- The installer preserves existing CLAUDE.md and .claude destinations; the inspected settings are project guidance, not tool permission grants or telemetry configuration.
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.52.2.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.52.2 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.