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
- 38
- First published
- Apr 2026
- Publisher
- jvs-milkdown
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":["@jvs-milkdown/[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":["@jvs-milkdown/[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
Scripts1
buildrollup -c
Dependencies14
@jvs-milkdown/exception^1.2.28prosemirror-changeset^2.3.1prosemirror-commands^1.7.1prosemirror-dropcursor^1.8.2prosemirror-gapcursor^1.4.0prosemirror-history^1.5.0prosemirror-inputrules^1.5.1prosemirror-keymap^1.2.3prosemirror-model^1.25.4prosemirror-schema-list^1.5.1prosemirror-state^1.4.4prosemirror-tables^1.8.1prosemirror-transform^1.10.5prosemirror-view^1.41.3