npm package reports / nexaapi

What ships in nexaapi?

nexaapi@1.0.0 ships 78 files, including 36 source map files.

“Official Node.js/TypeScript SDK for NexaAPI — AI image generation, video generation, text-to-speech, and more. Supports Flux, Stable Diffusion, Kling, Veo, ElevenLabs, and 56+ AI models.”

1.0.0version
78files
166.8 KBunpacked
1,324weekly dl

Findings

Maintainer fix: keep these out of the next nexaapi release
1. Append to .npmignore
# source maps
*.map
2. Verify before publishing
npm pack --dry-run --json | jq -r '.[0].files[].path' | grep -E '(^|/)[^/]*\.map$' || echo "clean"

Is a shipped source map a problem?

It depends. If the package is open source, the original code is public anyway, and the maps just add install size and can help with debugging. For proprietary or closed-source packages it's a real leak: a source map with sourcesContent lets anyone rebuild the original, unminified code, including comments and internal file names. This is how a major AI CLI's full source was exposed through npm in 2026.

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 nexaapi 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 nexaapi

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

Other package reports

chalk · @octokit/types · @inquirer/figures · progress · @ai-sdk/provider-utils · cli-truncate · fast-string-width · @inquirer/prompts · import-local · ansis · uglify-js · supports-hyperlinks

Automated heuristic scan of the public tarball for nexaapi@1.0.0, run on 2026-11-20. 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.