PkgRadar

Package evidence

@otr-app/[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
15Established · −30% score
First published
May 2022
Publisher
morkos

Effective trust discount applied: −30% (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":["@otr-app/[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":["@otr-app/[email protected]"],"fail_on":"review"}'
Publishermorkos
Artifact bytes81,293
Previous version2.0.2
Published2023-02-20T19:25:05.562Z
SHA-256001fe42266c10247cd548fd921fa1749ecca088d60d81f4b78ced27b740a079d

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

Scripts7
  • analyzewebpack --profile --json --analyze > stats.json && npm run stats
  • buildwebpack build --progress --mode=production && tsc
  • build:devowebpack build --progress --mode=development && tsc
  • preparehusky install
  • prepublishOnlykarma start && npm run build
  • statswebpack-bundle-analyzer build/stats.json
  • testkarma start