@deftai/directive-content@0.116.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 trigger, self-dependency, exfiltration, remote payload loading, or automatic control-surface mutation. The executable content is package-aligned task and Git-hook support that is activated only after explicit setup.
Decision evidence
public snapshot- The manifest defines only pack-time scripts and no preinstall, install, or postinstall hook.
- The flagged shell helper only resolves a CLI when an already-configured Git hook invokes it; it has no network, harvesting, or persistence behavior.
- No dependencies or self-dependency on this package are declared.
- The package ships Git hook and task automation content that can run after explicit user setup.
- Its prepack script spawns a local staging runner during package publication.
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 only resolves a CLI when an already-configured Git hook invokes it; it has no network, harvesting, or persistence behavior.
.githooks/_deft-run.shView on unpkg · L31Findings
Affected versions and remediation
This report applies to @deftai/directive-content@0.116.0.
See all versions of @deftai/directive-content for other recorded verdicts.
- Review the evidence and your use of @deftai/directive-content@0.116.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.