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
- 4
- First published
- Oct 2019
- Publisher
- federicoweber
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":["@bufferapp/[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":["@bufferapp/[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
linteslint . --ignore-pattern coverage node_modulesstartstart-storybook -p 9001testsh ../../package_test.sh
Dependencies10
@bufferapp/add-report^1.15.3@bufferapp/analyze-csv-export^1.15.1@bufferapp/analyze-date-picker^1.15.3@bufferapp/analyze-decorators^1.15.0@bufferapp/analyze-png-export^1.15.1@bufferapp/analyze-profile-selector^1.15.3@bufferapp/analyze-shared-components^1.15.3@bufferapp/async-data-fetch0.5.36-beta01@bufferapp/react-simple-dropdown3.2.5react-highcharts^16.0.2