@deftai/directive-content@0.109.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-aiThe only manifest scripts are pack-time hooks, and the flagged shell file is an inert helper until separately sourced by a Git hook. Static source inspection found no concrete malicious behavior.
Decision evidence
public snapshot- The manifest contains only prepack and postpack scripts, not npm install lifecycle hooks.
- The flagged shell helper resolves and invokes a CLI only when a Git hook explicitly sources it; it contains no network or file-write operation.
- No preinstall, install, or postinstall hook is declared.
- No runtime self-dependency is declared.
- No credential harvesting, exfiltration endpoint, obfuscated payload, or automatic agent-control-surface mutation was found.
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 unpkgThe flagged shell helper resolves and invokes a CLI only when a Git hook explicitly sources it; it contains no network or file-write operation.
.githooks/_deft-run.shView on unpkg · L16Findings
Affected versions and remediation
This report applies to @deftai/directive-content@0.109.0.
See all versions of @deftai/directive-content for other recorded verdicts.
- Review the evidence and your use of @deftai/directive-content@0.109.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.