npm package reports / @nestjs/schematics

What ships in @nestjs/schematics?

@nestjs/schematics@12.0.13 ships a clean tarball: 283 files, nothing unexpected.

“The generators behind the Nest CLI: scaffold NestJS applications, libraries, modules, controllers, services and CRUD resources.”

12.0.13version
283files
292.2 KBunpacked
14Mweekly 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/schematics 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/schematics

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

Other package reports

@nestjs/cli · @nestjs/http-client · 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/schematics@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.