npm package reports / facebook-nodejs-business-sdk
What ships in facebook-nodejs-business-sdk?
facebook-nodejs-business-sdk@26.0.3 ships 1389 files, including 6 source map files.
“SDK for the Facebook Marketing API in Javascript and Node.js”
Findings
- 6×Source map published (6 files)
dist/amd.js.map (+5 similar)Source maps expose original file names and structure, and can reconstruct source. Strip *.map from release builds or upload them privately to your error tracker. - 2×CI / infra configuration
.github/workflows/ci-publish.yml.github/workflows/ci.ymlInfra config can reveal internal hostnames, account IDs and deployment topology. - 1×IDE / OS metadata
.vscode/settings.jsonEditor and OS files leak local paths and usernames.
1. Append to .npmignore# source maps
*.map
# CI/infra config
.github/
.gitlab-ci.yml
.circleci/
docker-compose*.yml
*.tfstate
*.tfvars
# editor files
.vscode/
.idea/
.DS_Store2. Verify before publishingnpm pack --dry-run --json | jq -r '.[0].files[].path' | grep -E '(^|/)[^/]*\.map$|(^|/)\.github/|(^|/)\.gitlab-ci\.yml$|(^|/)\.circleci/|(^|/)docker-compose[^/]*\.yml$|(^|/)[^/]*\.tfstate$|(^|/)[^/]*\.tfvars$|(^|/)\.vscode/|(^|/)\.idea/|(^|/)\.DS_Store$' || echo "clean"- If package.json has a "files" field, npm ignores .npmignore. Narrow "files" instead, e.g. "files": ["dist", "!dist/**/*.map"].
- A new .npmignore replaces .gitignore for npm. Copy over anything from .gitignore you still want excluded.
- Or stop emitting maps for release builds: "sourceMap": false in tsconfig, or your bundler's equivalent.
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 facebook-nodejs-business-sdk 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/facebook-nodejs-business-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 facebook-nodejs-business-sdk@26.0.3, 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.