@deftai/directive-content@0.115.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 1mo ago · by lpm-firewall-aiSource inspection found no registry install lifecycle, runtime self-dependency, network behavior, secret harvesting, or destructive consumer-project mutation. The executable-looking shell file is a transparent Git-hook resolver rather than an inert or staged payload.
Decision evidence
public snapshot- The manifest defines only pack-time scripts, with no preinstall, install, or postinstall hook.
- The shipped Git hook helper invokes an existing Deft CLI only when a Git hook calls it.
- No install-time execution, self-dependency, network endpoint, credential collection, or exfiltration was found.
- The hook resolver checks local paths or PATH and otherwise exits with an error.
- The pack helper runs only during package creation and targets an adjacent source checkout.
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 shipped Git hook helper invokes an existing Deft CLI only when a Git hook calls it.
Findings
Affected versions and remediation
This report applies to @deftai/directive-content@0.115.0.
See all versions of @deftai/directive-content for other recorded verdicts.
- Review the evidence and your use of @deftai/directive-content@0.115.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.