npm package reports / log-update
What ships in log-update?
log-update@8.0.0 ships a clean tarball: 5 files, nothing unexpected.
“Log by overwriting the previous output in the terminal. Useful for rendering progress bars, animations, etc.”
Findings
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 log-update live
Maintainer? Show it in your README
The badge reflects the latest automated scan of the published tarball and refreshes on its own.
[](https://release-shield-app.vercel.app/npm/log-update?ref=badge)Other package reports
chalk · @octokit/types · @inquirer/figures · progress · cli-truncate · fast-string-width · @inquirer/prompts · import-local · ansis · uglify-js · supports-hyperlinks · @inquirer/select
Automated heuristic scan of the public tarball for log-update@8.0.0, 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.