PkgRadar

Package evidence

[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.

Weekly downloads
12,778Mainstream · −50% score
Versions published
24Mature · −50% score
First published
Oct 2014
Publisher
ui5-bot

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":["[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":["[email protected]"],"fail_on":"review"}'
Publisherui5-bot
Artifact bytes18,958
Previous version0.18.2
Published2022-05-19T13:57:55.479Z
SHA-256c275352de389bfdf91e5ef6275a7de7624c83fd4f61b3fd8c60a5b55d51a2013

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
0.18.3Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts9
  • coveragenyc npm run unit
  • depcheckdepcheck
  • linteslint ./
  • postversiongit push --follow-tags
  • preversionnpm test
  • release-notegit-chglog -c .chglog/release-config.yml v$npm_package_version
  • testnpm run lint && npm run coverage && npm run depcheck
  • unitgrunt
  • versiongit-chglog --next-tag v$npm_package_version -o CHANGELOG.md v0.16.0.. && git add CHANGELOG.md
Dependencies11
  • async^3.2.3
  • connect-inject^0.4.0
  • connect-openui5^0.10.2
  • cors^2.8.5
  • less-openui5^0.11.2
  • maxmin^3.0.0
  • pretty-data^0.40.0
  • serve-static^1.15.0
  • slash^3.0.0
  • terser^5.13.1
  • urljoin^0.1.5