PkgRadar

Package evidence

@syncfusion/[email protected]

no findings

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
79Mature · −50% score
First published
Dec 2024
Publisher
syncfusion-javascript

Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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":["@syncfusion/[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":["@syncfusion/[email protected]"],"fail_on":"review"}'
Publishersyncfusion-javascript
Artifact bytes2,871,550
Previous version33.2.8
Published2026-06-02T05:22:08.242Z
SHA-256a5e473b6e12da81ad917c8b58b2a0cec7a372b3b803722c9f3ef4d77dc6e0430

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

low
Last checked
lowRisk
0Score
33.2.10Version
Status history (3 events)
  1. scan_error → available · risk low · score 0 · status scan_error -> available, risk none -> low, score none -> 0
  2. new → scan_error · risk none · score — · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/@syncfusion/ej2-tailwind3-dark-theme/-/ej2-tailwind3-dark-theme-33.2.10.tgz)
  3. new → scan_error · risk none · score — · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/@syncfusion/ej2-tailwind3-dark-theme/-/ej2-tailwind3-dark-theme-33.2.10.tgz)

Evidence

Static findings

No findings stored for this release.