@deftai/directive-content
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.
This report shows the evidence for @deftai/directive-content@0.119.5. 3 of 61 known versions are blocked or flagged. The newest version, 0.126.2, is allowed. See all versions.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest contains a concrete destructive pack-time action that removes nearly every entry in its own package directory. This supports blocking publication despite the absence of install lifecycle hooks.
Decision evidence
public snapshot- `package.json` registers a `postpack` script that recursively removes every entry in the package directory except `package.json` and `stage-pack.mjs`.
- The cleanup runs after the package-pack operation and can erase the package directory’s other contents.
- The manifest declares no `preinstall`, `install`, or `postinstall` hook.
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.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing @deftai/directive-content@0.119.5. 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.