PkgRadar

Package evidence

@azure/[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
519Mature · −50% score
First published
Nov 2018
Publisher
microsoft1es

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":["@azure/[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":["@azure/[email protected]"],"fail_on":"review"}'
Publishermicrosoft1es
Artifact bytes278,005
Previous version9.1.2-alpha.20260310.1
Published2026-06-04T07:22:52.792Z
SHA-256e2466f79fc7b668ae57627712da1a91eb647770b570d510c44bb48981bfb8c9f

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

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts15
  • buildnpm run clean && dev-tool run build-package && dev-tool run extract-api
  • build:samplestsc -p config/tsconfig.samples.json && dev-tool samples publish -f
  • check-formatprettier --list-different --config ../../../.prettierrc.json --ignore-path ../../../.prettierignore "src/**/*.{ts,cts,mts}" "test/**/*.{ts,cts,mts}" "*.{js,cjs,mjs,json}" "samples-dev/*.ts"
  • cleanrimraf --glob dist dist-browser dist-esm test-dist temp types *.tgz *.log
  • execute:samplesdev-tool samples run samples-dev
  • extract-apirimraf review && dev-tool run extract-api
  • formatprettier --write --config ../../../.prettierrc.json --ignore-path ../../../.prettierignore "src/**/*.{ts,cts,mts}" "test/**/*.{ts,cts,mts}" "*.{js,cjs,mjs,json}" "samples-dev/*.ts"
  • generate:clientecho skipped
  • lintecho skipped
  • lint:fixecho skipped
  • packpnpm pack 2>&1
  • testtsc -b --noEmit && npm run test:node && npm run test:browser
  • test:browserdev-tool run test:vitest --browser
  • test:nodedev-tool run test:vitest
  • update-snippetsdev-tool run update-snippets
Dependencies8
  • @azure-rest/core-client^2.3.1
  • @azure/abort-controller^2.1.2
  • @azure/core-auth^1.9.0
  • @azure/core-lro^3.1.0
  • @azure/core-rest-pipeline^1.20.0
  • @azure/core-util^1.12.0
  • @azure/logger^1.2.0
  • tslib^2.8.1