PkgRadar

Package evidence

@expo/[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
7
First published
Oct 2019
Publisher
dsokal

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":["@expo/[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":["@expo/[email protected]"],"fail_on":"review"}'
Publisherdsokal
Artifact bytes8,067
Previous version0.2.4
Published2020-01-14T13:27:51.365Z
SHA-256d7becdb41999257006964950dd0c4755bdc3c79477ec7d287fe5c40f1db3e199

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.2.5Version
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

Scripts6
  • buildtsc
  • cleanrm -rf build ./tsconfig.tsbuildinfo
  • linteslint .
  • prepareyarn run clean && yarn build
  • testjest
  • watchtsc --watch
Dependencies2
  • fs-extra^7.0.1
  • xml2js^0.4.23