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.
- Versions published
- 8
- First published
- May 2025
- Publisher
- davidcoxon-of
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":["@openfin/[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":["@openfin/[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
Scripts3
buildnpm run build:tsbuild:tstsc --noEmit && tsup --dts-resolvepostbuildnode --experimental-strip-types ./scripts/load-assets.ts
Dependencies12
@openfin/core42.100.99@rollup/plugin-commonjs^25.0.7@rollup/plugin-node-resolve^15.2.3@rollup/plugin-typescript^11.1.6commander^13.1.0cosmiconfig^9.0.0cosmiconfig-typescript-loader^6.1.0rollup^4.9.1rollup-plugin-copy^3.5.0ts-node^10.9.2typescript^5.3.3zod^3.25.63