npm package reports / @buildvision/nest-sdk-generator

What ships in @buildvision/nest-sdk-generator?

@buildvision/nest-sdk-generator@3.0.0 ships 106 files; 1 item worth a look.

“Generate fully-typed RTK Query API clients from NestJS controllers”

3.0.0version
106files
578.7 KBunpacked
18Kweekly dl

Findings

Maintainer fix: keep these out of the next @buildvision/nest-sdk-generator release
1. Append to .npmignore
# CI/infra config
.github/
.gitlab-ci.yml
.circleci/
docker-compose*.yml
*.tfstate
*.tfvars
2. Verify before publishing
npm pack --dry-run --json | jq -r '.[0].files[].path' | grep -E '(^|/)\.github/|(^|/)\.gitlab-ci\.yml$|(^|/)\.circleci/|(^|/)docker-compose[^/]*\.yml$|(^|/)[^/]*\.tfstate$|(^|/)[^/]*\.tfvars$' || echo "clean"

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 @buildvision/nest-sdk-generator 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 @buildvision/nest-sdk-generator

[![ReleaseShield](https://release-shield-app.vercel.app/api/badge/npm/@buildvision/nest-sdk-generator.svg)](https://release-shield-app.vercel.app/npm/@buildvision/nest-sdk-generator?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 @buildvision/nest-sdk-generator@3.0.0, 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.