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
- 79Established · −30% score
- First published
- Oct 2025
- Publisher
- extedcoud
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 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":["@ondc/[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":["@ondc/[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
Scripts26
buildnpm run clean && tscbuild:watchtsc --watchcleanrm -rf dist coverage browser-distdevtsc --watchdocs:generatetypedoc src/index.ts --out docsformatprettier --write src/**/*.ts README.mdformat:checkprettier --check src/**/*.ts README.mdhelpers:gennode scripts/generate-helpers-source.jslinteslint src/**/*.ts --fixlint:checkeslint src/**/*.tsprebuildnpm run helpers:genpreparenpm run clean && npm run buildprepublishOnlynpm run test && npm run buildpretestnpm run helpers:genrelease:majornpm version major && npm publishrelease:minornpm version minor && npm publishrelease:patchnpm version patch && npm publishsecurity:auditnpm audit --audit-level highstartnode dist/index.jstestjesttest:browser-mockjest --testNamePattern="BrowserRunner|CrossEnvironment"test:cijest --ci --coverage --watchAll=falsetest:coveragejest --coveragetest:watchjest --watchtype-checktsc --noEmitvalidatenpm run type-check && npm run lint:check && npm run format:check
Dependencies8
acorn^8.15.0acorn-walk^8.3.4ajv^8.18.0base-64^1.0.0jsonpath^1.1.1terser^5.44.1uuid^10.0.0zod^4.1.12