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
- 1
- First published
- Jun 2026
- Publisher
- eterno25
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":["@zjedene-medusa/[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":["@zjedene-medusa/[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
Scripts3
buildyarn run -T rimraf dist && yarn run -T tsc --buildtest../../../node_modules/.bin/jest --passWithNoTests srcwatchyarn run -T tsc --watch
Dependencies24
@types/express^4.17.21@zjedene-medusa/deps2.15.5@zjedene-medusa/telemetry2.15.5@zjedene-medusa/utils2.15.5chalk^4.1.2configstore^5.0.1dotenv^16.4.5execa^5.1.1express^4.21.0fs-exists-cached^1.0.0fs-extra^11.1.1glob13.0.6hosted-git-info^4.0.2inquirer^8.0.0is-valid-path^0.1.1meant^1.0.3ora^5.4.1pg-god^1.0.12prompts^2.4.2resolve-cwd^3.0.0stack-trace^0.0.10ulid^2.3.0winston^3.9.0yargs^17.7.2