npm package reports / @nestjs/cli

What ships in @nestjs/cli?

@nestjs/cli@12.0.13 ships a clean tarball: 259 files, nothing unexpected.

“The Nest CLI: create NestJS applications, generate modules, controllers and CRUD resources, and build, run and watch projects and monorepos.”

12.0.13version
259files
338.1 KBunpacked
12Mweekly dl

Findings

✓ No source maps, environment files, credentials, internal docs or other unexpected files in the published tarball.

Keep it this way: check every release in CI

This report covers one published version. ReleaseShield runs on every publish. It scans the exact tarball (npm pack), wheel or Docker image your pipeline builds and fails the release before anything unexpected reaches the registry.

# .github/workflows/release.yml
- uses: my2ctyw8h6-hash/release-shield@v1
  with:
    fail-on: high
  env:
    RELEASESHIELD_TOKEN: ${{ secrets.RELEASESHIELD_TOKEN }}

See plans: from $19/mo Re-scan @nestjs/cli live

Maintainer? Show it in your README

The badge reflects the latest automated scan of the published tarball and refreshes on its own. ReleaseShield report for @nestjs/cli

[![ReleaseShield](https://release-shield-app.vercel.app/api/badge/npm/@nestjs/cli.svg)](https://release-shield-app.vercel.app/npm/@nestjs/cli?ref=badge)

Other package reports

@nestjs/http-client · @nestjs/schematics · chalk · @octokit/types · @inquirer/figures · progress · cli-truncate · fast-string-width · @inquirer/prompts · import-local · ansis · uglify-js

Automated heuristic scan of the public tarball for @nestjs/cli@12.0.13, run on 2026-11-17. Findings describe file contents and are not a judgment of the package's security or its maintainers; many are intentional. Maintainer and want this report removed or refreshed? Open an issue at github.com/my2ctyw8h6-hash/release-shield.