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
- 403
- Versions published
- 82Established · −30% score
- First published
- Sep 2025
- Publisher
- GitHub ActionsTrusted automation · −70% score
Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@ni/[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":["@ni/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Large Javascript Payload: 3907062 bytes
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 review · score 3 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Large Javascript Payload | package/dist/all-components-bundle.js | 3907062 bytes | 10 |
Manifest
Package metadata
Scripts17
buildnpm run build:components && npm run build:cembuild-bundlerollup --configbuild:cemnpm run build:cem:config && npm run build:cem:markdownbuild:cem:configcem analyze --config ./custom-elements-manifest.config.mjsbuild:cem:markdownnode build/generate-markdown.mjsbuild:componentstsc -p ./tsconfig.jsonformateslint . --fixinvoke-publishnpm publishlinteslint .packnpm packtestconcurrently --pad-prefix --timings --group "npm:test-chrome" "npm:test-webkit"test-chromekarma start karma.conf.headless.cjs --browsers=ChromeHeadlessOpt --single-run --skip-tags SkipChrometest-chrome-debuggerkarma start karma.conf.cjs --browsers=ChromeDebugging --skip-tags SkipChrometest-firefoxkarma start karma.conf.headless.cjs --browsers=FirefoxHeadless --single-run --skip-tags SkipFirefoxtest-firefox-debuggerkarma start karma.conf.cjs --browsers=FirefoxDebugging --skip-tags SkipFirefoxtest-webkitkarma start karma.conf.headless.cjs --browsers=WebkitHeadless --single-run --skip-tags SkipWebkittest-webkit-debuggerkarma start karma.conf.cjs --browsers=WebkitDebugging --skip-tags SkipWebkit
Dependencies6
@ni/fast-element^10.1.1@ni/fast-foundation^10.2.3@ni/fast-web-utilities^10.0.0@ni/nimble-components^35.9.3@ni/spright-components^6.19.1tslib^2.2.0