@rowansenne/docnexus@0.24.3
[English README](./README.md)
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe install hook performs an automatic destructive cleanup of legacy project directories without migrating their contents or requiring confirmation. The legacy checks limit its scope, but do not prevent data loss for users upgrading through installation.
Decision evidence
public snapshot- The manifest runs a postinstall script during package installation.
- The hook resolves the consuming project and calls legacy cleanup for local installs.
- Cleanup checks for legacy project directories, then recursively deletes them without migrating their contents.
- The cleanup routine describes the transition as destructive and removes the legacy workspace directory.
- Cleanup is limited to directories that pass legacy-format checks; it does not target arbitrary project directories.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe manifest runs a postinstall script during package installation.
package.jsonView on unpkg · L43Install-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.3.
See all versions of @rowansenne/docnexus for other recorded verdicts.
- Avoid installing @rowansenne/docnexus@0.24.3. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.