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
- 2
- First published
- Jun 2026
- Publisher
- dmytrimusiiko
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":["@scaleflex/[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":["@scaleflex/[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
Scripts16
buildnpm run build:bundle && npm run build:react && npm run build:filerobot && node scripts/verify-bundle.mjsbuild:bundlevite build --config config/vite.config.tsbuild:demovite build --config config/vite.demo.config.tsbuild:filerobotvite build --config config/vite.filerobot.config.tsbuild:reactvite build --config config/vite.react.config.tsbuild:react-demovite build --config config/vite.react-demo.config.tsdevvite --config config/vite.demo.config.tsdev:reactvite --config config/vite.react-demo.config.tslinteslint src/ tests/ --ext .ts,.tsxprepublishOnlynpm run buildreleasenode scripts/release-cdn.mjs pluginsandboxvite --config sandbox/vite.config.tstestvitest runtest:coveragevitest run --coveragetest:watchvitesttypechecktsc --noEmit