@rowansenne/docnexus@0.24.2
[English README](./README.md)
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe postinstall hook can delete recognized legacy DocNexus data without migration or confirmation, creating a concrete data-loss risk. Its narrow product-specific scope makes malicious intent unproven, so this warrants a warning rather than a block.
Decision evidence
public snapshot- package.json runs scripts/postinstall.mjs on installation.
- The install hook invokes cleanupLegacyProject for a local project installation.
- The cleanup recognizes older DocNexus project formats and can recursively remove legacy project data without migration.
- The cleanup also removes entries from .docnexus that are outside its installation allowlist.
- Agent skill linking and instruction-file updates occur through the explicit skills link command, not the install hook.
- The cleanup is restricted to identified DocNexus legacy directories; the source does not show broad deletion outside them.
Source & flagged code
5 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 @rowansenne/docnexus@0.24.2.
See all versions of @rowansenne/docnexus for other recorded verdicts.
- Review the evidence and your use of @rowansenne/docnexus@0.24.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.