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
- 5
- First published
- Jan 2022
- Publisher
- lifescience
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
Scripts8
buildcross-env NODE_ENV=production rollup -c -m trueprettierprettier --check 'src/**/*.{js,jsx,json,ts,tsx}'prettier:writeprettier --write 'src/**/*.{js,jsx,json,ts,tsx}'startcross-env NODE_ENV=development rollup -c -m true -wtestrun-s prettier test:lint test:unittest:linteslint src --ext .ts,.tsx,.js,.jsxtest:unitjesttest:unit:updatejest -u
Dependencies12
@babel/runtime^7.12.5@emotion/react^11.7.1@emotion/styled^11.6.0@mui/material^5.2.5@reduxjs/toolkit^1.7.1clsx^1.1.1lodash^4.17.21miew0.10.1react-redux^7.2.6redux^4.1.2redux-saga^1.1.3use-resize-observer^7.0.0