npm package reports / mock-aws-s3

What ships in mock-aws-s3?

mock-aws-s3@4.0.2 ships 2959 files; 1 item worth a look.

“Mock AWS S3 SDK for Node.js”

4.0.2version
2,959files
103.8 KBunpacked
0weekly dl

Findings

1 additional match for secret patterns or sensitive file types was not published here. Many are test fixtures or documentation examples; we never list details of possible credentials publicly. Maintainers can see the details with a live scan.

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 mock-aws-s3 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 mock-aws-s3

[![ReleaseShield](https://release-shield-app.vercel.app/api/badge/npm/mock-aws-s3.svg)](https://release-shield-app.vercel.app/npm/mock-aws-s3?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 mock-aws-s3@4.0.2, 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.