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
- 14
- First published
- May 2026
- Publisher
- teimurjan
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":["@blazediff/[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":["@blazediff/[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
Scripts7
buildtsup && vite buildcleanrm -rf dist SKILL.md JUDGING.md MASKING.mddevtsup --watchdev:clientviteprebuildnode -e "const {readdirSync,copyFileSync}=require('node:fs');for(const f of readdirSync('../../skill/blazediff'))if(f.endsWith('.md')&&f!=='INSTALL.md')copyFileSync('../../skill/blazediff/'+f,f)"testvitest run --passWithNoTeststypechecktsc --noEmit
Dependencies10
@blazediff/core-native5.1.0@langchain/core^1.1.44@langchain/langgraph^1.3.0@langchain/langgraph-checkpoint^1.0.2commander^13.1.0picocolors^1.1.1playwright^1.50.0sharp^0.34.0tree-kill^1.2.2zod^3.25.32