@rowansenne/docnexus@0.16.0
[English README](./README.md)
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe manifest has no consumer install hook, and source tracing shows agent configuration changes are tied to explicit project setup commands. The inspected integration and bundled instructions did not establish a concrete attack surface.
Decision evidence
public snapshot- package.json defines a CLI entry point and build/prepack scripts; it has no consumer install lifecycle hook.
- Agent context selects a project instruction file, and the writer updates that file with a marked DocNexus section.
- Agent links are created by explicit initialization with selected agents or by the skills-link command; initialization defaults to no agents.
- The setup copies packaged skills into the project workspace and links them into the selected agent directory.
- Inspected source does not establish install-time agent configuration mutation, credential transfer, or data exfiltration.
- The bundled entry skill limits capture to after user agreement and describes recall as read-only.
Source & flagged code
6 flagged · loading sourceManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
dist/src/skills.jsView on unpkgFindings
Affected versions and remediation
This report applies to @rowansenne/docnexus@0.16.0.
See all versions of @rowansenne/docnexus for other recorded verdicts.
- Review the evidence and your use of @rowansenne/docnexus@0.16.0 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.