npm package reports / wildberries-sdk

What ships in wildberries-sdk?

wildberries-sdk@0.1.189 ships a clean tarball: 2515 files, nothing unexpected.

“Wildberries API SDK for Node.js and TypeScript: typed clients for the Wildberries seller API, regenerated from the official OpenAPI specs on every change.”

0.1.189version
2,515files
11.8 MBunpacked
0weekly 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 wildberries-sdk 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 wildberries-sdk

[![ReleaseShield](https://release-shield-app.vercel.app/api/badge/npm/wildberries-sdk.svg)](https://release-shield-app.vercel.app/npm/wildberries-sdk?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 wildberries-sdk@0.1.189, run on 2026-11-18. 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.