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
- 1
- First published
- Jun 2026
- Publisher
- libretimes
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":["@libretimes/[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":["@libretimes/[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
Scripts5
buildtscpreparenpm run buildprepublishOnlynpm run build && npm testtestvitest runtest:watchvitest
Dependencies20
@libretimes/rehype-katex-scroll>=0.1.0@libretimes/remark-video>=0.1.0hast-util-sanitize>=5katex>=0.16rehype-autolink-headings>=7rehype-external-links>=3rehype-katex>=7rehype-pretty-code>=0.14rehype-raw>=7rehype-sanitize>=6rehype-slug>=6remark-deflist>=1remark-directive>=4remark-flexible-code-titles>=1remark-gfm>=4remark-math>=6remark-smartypants>=3remark-supersub>=1shiki>=1unist-util-visit>=5