npm package reports / progress

What ships in progress?

progress@2.0.3 ships a clean tarball: 7 files, nothing unexpected.

“Flexible ascii progress bar”

2.0.3version
7files
15.1 KBunpacked
79Mweekly 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 progress 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 progress

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

Other package reports

chalk · @octokit/types · @inquirer/figures · cli-truncate · fast-string-width · @inquirer/prompts · import-local · ansis · uglify-js · supports-hyperlinks · @inquirer/select · log-update

Automated heuristic scan of the public tarball for progress@2.0.3, 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.