create-newt-app@0.32.1
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found opt-outtable, product-aligned usage telemetry activated by a completed CLI run, with no credential or file-content collection in its payload. The scanner's credential-exfiltration hint is not supported by the inspected source.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and has no install lifecycle hook; its dependencies are declared normally.
- When the CLI completes project creation, it sends usage data to the Newt telemetry endpoint. The payload contains CLI and Node versions, platform, CI category, mode, flags, and project feature selections.
- Telemetry can be disabled with standard tracking opt-outs or Newt-specific environment settings. The inspected payload does not include credentials, file contents, or host identifiers.
- The prepared prompt, color, and command-line dependencies have ordinary package entrypoints and no install hooks in their inspected manifests; their cited entry files show prompt UI, color formatting, and named command-line exports.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L7A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to create-newt-app@0.32.1.
See all versions of create-newt-app for other recorded verdicts.
- Review the evidence and your use of create-newt-app@0.32.1 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.