npm package reports / @angular/cli

What ships in @angular/cli?

@angular/cli@22.2.7 ships 351 files, including 109 source map files.

“CLI tool for Angular”

22.2.7version
351files
1.5 MBunpacked
7.3Mweekly dl

Findings

Maintainer fix: keep these out of the next @angular/cli release
1. Append to .npmignore
# source maps
*.map
2. Verify before publishing
npm pack --dry-run --json | jq -r '.[0].files[].path' | grep -E '(^|/)[^/]*\.map$' || echo "clean"

Is a shipped source map a problem?

It depends. If the package is open source, the original code is public anyway, and the maps just add install size and can help with debugging. For proprietary or closed-source packages it's a real leak: a source map with sourcesContent lets anyone rebuild the original, unminified code, including comments and internal file names. This is how a major AI CLI's full source was exposed through npm in 2026.

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 @angular/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 @angular/cli

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

Other package reports

@angular/build · chalk · @octokit/types · @inquirer/figures · progress · cli-truncate · fast-string-width · @inquirer/prompts · import-local · ansis · uglify-js · supports-hyperlinks

Automated heuristic scan of the public tarball for @angular/cli@22.2.7, 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.