@rowansenne/docnexus@0.18.0
[English README](./README.md)
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and agent configuration changes are tied to explicit project setup or linking. The inspected writes are scoped to DocNexus project skills and a marked project instruction block, so the scanner hints do not establish an attack.
Decision evidence
public snapshot- package.json exposes the CLI and lists prepack as a build step; it has no install lifecycle hook.
- Agent skill links target project-local .agents/skills or .claude/skills directories.
- Agent context updates are reached through the skills-link path and replace or add only the marked DocNexus block in a project instruction file.
- CLI initialization defaults to no agent targets; agent linking requires an explicit target, and reset requires --force.
- Skill synchronization copies files into the project-local docnexus/skills workspace.
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 unpkgAgent skill links target project-local .agents/skills or .claude/skills directories.
dist/src/skills.jsView on unpkg · L24Findings
Affected versions and remediation
This report applies to @rowansenne/docnexus@0.18.0.
See all versions of @rowansenne/docnexus for other recorded verdicts.
- Review the evidence and your use of @rowansenne/docnexus@0.18.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.