domma-js@0.52.4
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection found an interactive postinstall offer to copy first-party project guidance and a separately invoked setup command. The scanner's high-risk labels are not supported by the inspected behavior, and the bundle excerpts show generic caller-directed HTTP helpers rather than a publisher-selected credential recipient.
Decision evidence
public snapshot- The postinstall hook asks whether to copy assistance files, and its copy routine creates a .claude directory only when one is absent.
- The CLI routes setup-ai as a separate command and preserves existing assistance files.
- The supplied Claude settings describe project paths, code preferences, and Domma aliases; they do not configure hooks or permissions.
- The inspected bundle HTTP helpers call fetch with a URL and options supplied to the helper; no credential collection or fixed publisher endpoint appears in those excerpts.
- The view template is a generated project example with placeholder values and sample lifecycle callbacks.
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.4.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.52.4 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.