registry / create-newt-app / 0.38.0
create-newt-app@0.38.0
Scaffold a pnpm workspace with Next.js, NestJS, Better Auth and Kysely, wired together.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest exposes a user-invoked scaffolding CLI with no install hook. Its telemetry is package-associated usage reporting, and the inspected payload and callers establish no credential theft, malicious execution, or other attack behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the CLI and scaffolding completes successfully.
Impact
The inspected payload does not include credentials or arbitrary environment values.
Mechanism
The CLI posts selected options and basic runtime metadata to its telemetry endpoint; supported environment settings can disable the report.
AI rationale
The manifest exposes a user-invoked scaffolding CLI with no install hook. Its telemetry is package-associated usage reporting, and the inspected payload and callers establish no credential theft, malicious execution, or other attack behavior.
Evidence
package.jsondist/index.js
Network endpoints1
newt-telemetry.newt-app.workers.dev
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes dist/index.js as the CLI entrypoint and lists no install lifecycle hook.
- After successful scaffolding, the CLI reports its version, platform, CI provider, flags, and selected scaffold options to the package-associated telemetry endpoint.
- Telemetry is skipped when the supported opt-out environment settings are enabled.
- The inspected dependency manifests and entrypoints show prompt, terminal styling, and command parsing libraries; their scripts contain no install lifecycle hook.
Evidence against
- The scanner's credential-exfiltration and sandbox-gating labels are not supported by the inspected source: the telemetry payload contains scaffold usage fields, not credentials or arbitrary environment values.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
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.38.0";
...
L259: <% } %>BETTER_AUTH_URL=http://localhost:3000
L260: BETTER_AUTH_SECRET=generate-with-openssl-rand-base64-32
L261: `
...
L393: // Load root .env first, then local .env (local takes precedence)
L394: 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.38.0";
...
L259: <% } %>BETTER_AUTH_URL=http://localhost:3000
L260: BETTER_AUTH_SECRET=generate-with-openssl-rand-base64-32
L261: `
...
L393: // Load root .env first, then local .env (local takes precedence)
L394: 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.38.0.
See all versions of create-newt-app for other recorded verdicts.
- Review the evidence and your use of create-newt-app@0.38.0 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.