Trust signals
Why this verdict
PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.
- Weekly downloads
- 11
- Versions published
- 3
- First published
- Mar 2021
- Publisher
- fabio.p
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
Block this release in CIcurl · GitHub Actions
Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer $PKGRADAR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"specs":["@jumpgroup/[email protected]"],"fail_on":"review"}'GitHub Actions step:
- name: PkgRadar gate
run: |
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
-H "Content-Type: application/json" \
-d '{"specs":["@jumpgroup/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
No high-signal static finding in the saved report.
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts25
browserstackbash ./etc/runBrowserstackSeq.shbrowserstack:fullbash ./etc/runFullBrowserstackSeq.shbrowserstack:remote-localhostbash ./etc/runBrowserstackLocal.shbuildnpm run build:clean && npm run build:check && npm run build:prod && npm run build:docsbuild:checknpm run eslintbuild:cleanrimraf dist/*build:debugcross-env NODE_ENV=debug webpack --config etc/webpack.config.jsbuild:devcross-env NODE_ENV=debug webpack --config etc/webpack.config.jsbuild:docsnode docs/asciidoc.jsbuild:prodcross-env-shell SNAPSHOT=${SNAPSHOT} NODE_ENV=production webpack --config etc/webpack.config.jsbuild:rainpm run build && rm -rf dist/demos && rm -rf dist/docs && rm -rf dist/release && rm dist/index.htmlbuild:releasenpm run build:clean && cross-env-shell SNAPSHOT=${SNAPSHOT} NODE_ENV=release webpack --config etc/webpack.config.js && npm run build:docs && node etc/file_stats.jsbuild:restartnpm run build:dev && npm run build:prod && npm startbuild:testnpm run build && rm -rf dist/demos && rm -rf dist/docs && rm -rf dist/releasebuild:watchwebpack-dev-server --inline --watch --config etc/webpack.config.jse2enightwatch -c etc/nightwatch.local.conf.js -e chromee2esafarinightwatch -c etc/nightwatch.local.conf.js -e safarieslinteslint "src/*.js" && eslint "src/scripts/*.js" && eslint "etc/*" && eslint "test/specs/**/*.js" && eslint "test/e2e/**/*.js"pree2emkdirp target/reports && node etc/nightwatch.local.conf.jsprepublishOnlynpm run buildstartnode http_server.jstest:nodemocha 3000 --exit test/nodetest:securitynpm audit --json | npm-audit-helper --prod-onlytest:seleniumnode etc/nightwatch.jenkins.conf.js && ./node_modules/.bin/nightwatch -c etc/nightwatch.jenkins.conf.js -e chromewatchcross-env NODE_ENV=development webpack-dev-server --hot --config etc/webpack.config.js --inline --progress --port 5000 --host 127.0.0.1 --disable-host-check
Dependencies6
browser-env^3.3.0consent-string1.4.2didomi-iabtcf-cmpapi1.1.4-1didomi-iabtcf-core1.1.4-1didomi-iabtcf-stub1.1.4js-cookie2.1.4