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
- 59
- Versions published
- 4
- First published
- Mar 2026
- Publisher
- dlovero-dialpad
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":["@dialpad/[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":["@dialpad/[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
Scripts15
buildrun-p build:*build:mainvite buildbuild:typesrun-p types:*coveragevitest run --coverage --passWithNoTestscoverage:openrushx coverage && open coverage/index.htmlformatprettier ./ --writeformat:ciprettier ./ --checklintecho 'needs migration to use @dialpad/eslint-config'lint:ciecho 'needs migration to use @dialpad/eslint-config'testvitesttest:cirushx test 2>&1typecheckrushx types:checktypecheck:cirushx typechecktypes:buildtsctypes:checktsc --noEmit
Dependencies2
@fluent/bundle0.17.1fluent-vue3.7.2