@deftai/directive-content@0.105.0
Shippable Directive framework content in the consumer .deft/core/ layout (C1 flatten), plus the engine surfaces (.githooks/, Taskfile.yml, tasks/) the deposit wires. Python-free per #2022 Phase 3. Refs #11, #1669, #1967.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an explicit, project-local hook setup rather than unconsented install-time mutation. It merits a warning for its persistent command-execution surface, not a block.
Decision evidence
public snapshot- `task setup` changes the current project's Git hooks path.
- Bundled hooks invoke the `deft` CLI on commits and pushes.
- No npm preinstall/install/postinstall lifecycle hook is declared.
- Only three shell files are executable; no payload binary or symlink was found.
- Reviewed hook code contains no network, credential harvesting, or exfiltration logic.
Source & flagged code
4 flagged · loading sourcePackage hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.
.githooks/_deft-run.shView on unpkgPackage ships non-JavaScript build or shell helper files.
.githooks/_deft-run.shView on unpkgFindings
Affected versions and remediation
This report applies to @deftai/directive-content@0.105.0.
See all versions of @deftai/directive-content for other recorded verdicts.
- Review the evidence and your use of @deftai/directive-content@0.105.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.