registry / create-newt-app / 0.31.10
create-newt-app@0.31.10
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe scanner’s credential-exfiltration hint is not supported by the inspected source: telemetry sends bounded scaffold metadata to a package-aligned endpoint after successful CLI use. The manifest has no install lifecycle hook, and the inspected telemetry path contains opt-outs and no credential transfer.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user invokes the CLI and scaffolding succeeds; telemetry is skipped when an inspected opt-out variable disables it.
Impact
The endpoint receives usage metadata; the inspected behavior does not establish credential theft, unrelated data collection, or another attack.
Mechanism
The CLI posts its version, platform, coarse CI provider, selected options, and explicit flags. The inspected payload does not include credentials or file contents.
AI rationale
The scanner’s credential-exfiltration hint is not supported by the inspected source: telemetry sends bounded scaffold metadata to a package-aligned endpoint after successful CLI use. The manifest has no install lifecycle hook, and the inspected telemetry path contains opt-outs and no credential transfer.
Network endpoints1
newt-telemetry.newt-app.workers.dev
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI entrypoint and contains no install lifecycle hook.
- The inspected prompt, terminal styling, and command parser dependencies expose their expected library entrypoints.
- The CLI sends version, platform, coarse CI provider, selected scaffold options, and explicit flags to its package-branded telemetry endpoint.
- Telemetry runs after successful scaffolding and has environment-variable opt-outs; no credential or file contents are included in its payload.
- The optional package installation command runs pnpm in the selected project directory.
Evidence against
Behavioral surface
CryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/index.jsView file
7import { randomBytes } from "node:crypto";
L8: import { execa } from "execa";
L9: import ejs from "ejs";
...
L11: import path from "path";
L12: import https from "node:https";
L13: //#region package.json
L14: var version = "0.31.10";
...
L208: <% } %>BETTER_AUTH_URL=http://localhost:3000
L209: BETTER_AUTH_SECRET=generate-with-openssl-rand-base64-32
L210: `
...
L350: // Load root .env first, then local .env (local takes precedence)
L351: dotenv.config({ path: resolve(process.cwd(), '../../.env') });
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L77Trigger-reachable chain: manifest.bin -> dist/index.js
L7: import { randomBytes } from "node:crypto";
L8: import { execa } from "execa";
L9: import ejs from "ejs";
...
L11: import path from "path";
L12: import https from "node:https";
L13: //#region package.json
L14: var version = "0.31.10";
...
L208: <% } %>BETTER_AUTH_URL=http://localhost:3000
L209: BETTER_AUTH_SECRET=generate-with-openssl-rand-base64-32
L210: `
...
L350: // Load root .env first, then local .env (local takes precedence)
L351: dotenv.config({ path: resolve(process.cwd(), '../../.env') });
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L7Findings
2 Critical2 High3 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
HighSandbox Evasion Gated Capabilitydist/index.js
HighTrigger Reachable Credential Exfiltrationdist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to create-newt-app@0.31.10.
See all versions of create-newt-app for other recorded verdicts.
- Review the evidence and your use of create-newt-app@0.31.10 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.