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
- 11
- Versions published
- 8
- First published
- Jun 2018
- Publisher
- ufe-keeper
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":["@everymatrix/[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":["@everymatrix/[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
buildnode ./node_modules/@everymatrix/ufe-babel/node_modules/.bin/babel src --out-dir lib --copy-filesem-publishnpm run eslint && npm run sasslint && npm run test && npm run buildeslintnode ./node_modules/@everymatrix/ufe-eslint/node_modules/.bin/eslint src __tests__ __mocks__ -c ./node_modules/@everymatrix/ufe-conf/.eslintrcsasslintnode ./node_modules/@everymatrix/ufe-react/node_modules/.bin/sass-lint -c ./node_modules/@everymatrix/ufe-conf/.sass-lint.yml "**/src/**/*.s?(a|c)ss" --verbose --no-exitsetup-devufe setup-devtestexit 0test:coveragenpm run test -- --coverage
Dependencies5
@everymatrix/ufe-components^0.1.2@everymatrix/ufe-core^0.1.2@everymatrix/ufe-react^0.1.2@everymatrix/ufe-utils^0.1.2@everymatrix/ufe-webapi^0.1.2