npm package reports / @splitsoftware/splitio-commons

What ships in @splitsoftware/splitio-commons?

@splitsoftware/splitio-commons@3.2.0 ships 852 files; 1 item worth a look.

“Split JavaScript SDK common components”

3.2.0version
852files
2.2 MBunpacked
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 @splitsoftware/splitio-commons 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 @splitsoftware/splitio-commons

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

Other package reports

@splitsoftware/splitio · @splitsoftware/splitio-react · chalk · @octokit/types · @inquirer/figures · progress · cli-truncate · fast-string-width · @inquirer/prompts · import-local · ansis · uglify-js

Automated heuristic scan of the public tarball for @splitsoftware/splitio-commons@3.2.0, 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.