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
- 1,757Niche · −30% score
- Versions published
- 111
- First published
- Feb 2026
- Publisher
- tripolskypetr
Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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":["@backtest-kit/[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":["@backtest-kit/[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
Scripts8
buildrollup -cbuild:copynode ./scripts/copy.mjsbuild:modulesnpm run build:modules:winbuild:modules:windotenv -e .env -- .\scripts\win\build.bat && npm run build:copy && npm run build:postbuildbuild:modules:xdotenv -e .env -- sh ./scripts/linux/build.sh && npm run build:copy && npm run build:postbuildbuild:postbuildnode ./scripts/postbuild.mjsservenode ./scripts/mock.mjsstartnpm run build && cross-env NODE_ENV=development CC_ENABLE_MOCK=1 npm run serve
Dependencies9
cryptocurrency-icons^0.18.1di-kit^1.1.1di-scoped^1.0.21finalhandler^1.3.1functools-kit^2.3.0get-moment-stamp^2.0.0micro^10.0.1router^1.3.8serve-handler^6.1.6