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
- 7
- First published
- Feb 2025
- Publisher
- tomharms
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":["@kaliber/[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":["@kaliber/[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
Scripts3
test$npm_execpath test-integration && $npm_execpath test-rulestest-integrationnode --test integration-test/test.jstest-rulesnode --test stylelint-plugins/rules/*/test.js
Dependencies11
@stylistic/stylelint-plugin^5.2.0postcss^8.5.15postcss-calc^10.1.1postcss-custom-media^12.0.1postcss-custom-properties^15.0.1postcss-custom-selectors^9.0.1postcss-modules-values^4.0.0postcss-selector-parser^7.0.0postcss-values-parser^8.0.0stylelint^17.12.0stylelint-use-nesting^6.0.0