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.

Weekly downloads
3,243Niche · −30% score
Versions published
443Mature · −50% score
First published
Aug 2021
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 bytes299,217
Previous version1.2.2-alpha.20260310.1
Published2026-03-11T13:16:47.300Z
SHA-25686c4691d1c01e57c49676b07779d7e30cfdc8a59197c7aed5ff38c9c2cb3661f

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
1.2.2-alpha.20260311.1Version
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

Scripts13
  • buildnpm run clean && dev-tool run build-package && dev-tool run extract-api
  • build:samplestsc -p tsconfig.samples.json && dev-tool samples publish -f
  • check-formatecho skipped
  • cleanrimraf --glob dist dist-browser dist-esm test-dist temp types *.tgz *.log
  • execute:samplesecho skipped
  • extract-apidev-tool run extract-api
  • formatecho skipped
  • lintecho skipped
  • packpnpm pack 2>&1
  • testnpm run test:node && npm run test:browser
  • test:browserecho skipped
  • test:nodedev-tool run build-test --no-browser-test && dev-tool run test:vitest
  • update-snippetsdev-tool run update-snippets
Dependencies7
  • @azure/abort-controller>=2.1.3-alpha <2.1.3-alphb
  • @azure/core-auth>=1.10.2-alpha <1.10.2-alphb
  • @azure/core-client>=1.10.2-alpha <1.10.2-alphb
  • @azure/core-lro^2.7.2
  • @azure/core-paging>=1.6.3-alpha <1.6.3-alphb
  • @azure/core-rest-pipeline>=1.23.1-alpha <1.23.1-alphb
  • tslib^2.8.1