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
- 7
- Versions published
- 4
- First published
- Apr 2023
- Publisher
- k8stack
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":["[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":["[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
Scripts11
buildtsc && vite builddeploypnpm build && npm publish --access publicdevvite --port 3333formatpnpm lint:styles && pnpm lint:scripts && prettier --write ./*.jsonlint:scriptseslint --fix 'src/**/**.{ts,tsx}' './.*.cjs' './*.{cjs,ts}'lint:stylesnpx stylelint --fix 'src/**/**.{css,style.ts,style.tsx}'prebuildrimraf ./buildpreviewvite previewsetup./scripts/nvm-use.sh && pnpm itestvitesttest:civitest --run
Dependencies5
@emotion/react^11.9.0@emotion/styled^11.8.1classnames^2.3.2react^18react-dom^18