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
- 39
- First published
- Apr 2026
- Publisher
- melaasar
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":["@oml/[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":["@oml/[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
Scripts4
buildecho 'No build step'build:cleannpm run clean && npm run buildcleanshx rm -fr *.tsbuildinfo outtestnode test/rest-gating.test.mjs && node test/rest-update-builds.test.mjs
Dependencies13
@leeoniya/ufuzzy^1.0.19@oml/language0.21.2@oml/markdown0.21.2@oml/owl0.21.2@oml/platform^0.8.0keytar^7.9.0langium4.2.1langium-cli^4.2.0markdown-it^14.1.1nunjucks^3.2.4swagger-ui-dist^5.32.4vscode-languageserver~9.0.1yaml^2.8.2