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
- 2
- Versions published
- 2
- First published
- May 2026
- Publisher
- ravindrakumar8088
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":["@frontguard/[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":["@frontguard/[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
Scripts7
buildtsupdevtsup --watchlinteslint src/prepublishOnlynpm run buildtestvitest run --pool=forks --exclude='test/e2e/**'test:e2evitest run --config vitest.e2e.config.tstypechecktsc --noEmit
Dependencies10
@daytonaio/sdk^0.180.0chalk^5.3.0commander^14.0.0hono^4.12.9ora^9.3.0pixelmatch^7.1.0playwright^1.59.0pngjs^7.0.0tsx^4.21.0zod^3.25.0
Optional dependencies2
@axe-core/playwright^4.10.0better-sqlite3^11.10.0