checklist-tui@0.1.4
Write a note. Get a checklist. Check things off in the terminal.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has an intrusive but package-aligned global-install welcome flow and a user-triggered generation request. Source inspection found no concrete malicious chain.
Decision evidence
public snapshot- A postinstall hook runs and, for global installs, opens the user's TTY, clears it, and starts the package CLI.
- The CLI can POST a user-provided checklist goal to its documented generation endpoint.
- Checklist data is stored locally under the user's config directory.
- No credential, environment, or arbitrary-file harvesting was found.
- No remote code loading, eval, shell execution, or unconsented agent-control-surface mutation was found.
- Network use is limited to an explicit checklist-generation action; child process use only plays a macOS sound or invokes explicit update/uninstall commands.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to checklist-tui@0.1.4.
See all versions of checklist-tui for other recorded verdicts.
- Review the evidence and your use of checklist-tui@0.1.4 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.