@deftai/directive-content@0.119.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 14d ago · by lpm-firewall-aiThe automatic postpack hook recursively deletes nearly the entire package directory, creating a concrete destructive action when packing is invoked. This warrants blocking publication as destructive behavior.
Decision evidence
public snapshot- The `postpack` script deletes every entry in the package directory except `package.json` and `stage-pack.mjs`, recursively and without prompting.
- No install lifecycle hook is declared; the destructive script runs after the user invokes the package-packing operation.
Source & flagged code
3 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.119.0.
See all versions of @deftai/directive-content for other recorded verdicts.
- Avoid installing @deftai/directive-content@0.119.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.