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
1,755Mature · −50% score
First published
Aug 2019
Publisher
azure-sdkTrusted automation · −70% score

Effective trust discount applied: −70% (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"}'
Publisherazure-sdk
Artifact bytes36,939
Previous version1.0.9-beta.20201116
Published2021-06-15T17:25:44.833Z
SHA-25670792da6d304bae4a5a6bd3da6692f8d1b90405e46bfef4a366e7a347557a075

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.0.11Version
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

Scripts28
  • auditnode ../../../common/scripts/rush-audit.js && rimraf node_modules package-lock.json && npm i --package-lock-only 2>&1 && npm audit
  • buildtsc -p . && npm run build:nodebrowser && api-extractor run --local && npm run build:types
  • build:browsertsc -p . && cross-env ONLY_BROWSER=true rollup -c 2>&1
  • build:nodetsc -p . && cross-env ONLY_NODE=true rollup -c 2>&1
  • build:nodebrowserrollup -c 2>&1
  • build:samplesecho Obsolete.
  • build:testtsc -p . && rollup -c 2>&1
  • build:typesdownlevel-dts types/latest types/3.1
  • check-formatprettier --list-different --config ../../../.prettierrc.json --ignore-path ../../../.prettierignore "src/**/*.ts" "test/**/*.ts" "*.{js,json}"
  • cleanrimraf dist dist-* temp types *.tgz *.log
  • docstypedoc --excludePrivate --excludeNotExported --excludeExternals --stripInternal --mode file --out ./dist/docs ./src
  • execute:samplesdev-tool samples run samples-dev
  • extract-apitsc -p . && api-extractor run --local
  • formatprettier --write --config ../../../.prettierrc.json --ignore-path ../../../.prettierignore "src/**/*.ts" "test/**/*.ts" "samples-dev/**/*.ts" "*.{js,json}"
  • generate:clientautorest --typescript --v3 swagger
  • integration-testnpm run integration-test:node && npm run integration-test:browser
  • integration-test:browserkarma start --single-run
  • integration-test:nodenyc mocha -r esm --require source-map-support/register --reporter ../../../common/tools/mocha-multi-reporter.js --timeout 5000000 --full-trace "dist-esm/test/{,!(browser)/**/}/*.spec.js"
  • linteslint package.json api-extractor.json src test --ext .ts
  • lint:fixeslint package.json api-extractor.json src test --ext .ts --fix --fix-type [problem,suggestion]
  • packnpm pack 2>&1
  • prebuildnpm run clean
  • testnpm run build:test && npm run unit-test && npm run integration-test
  • test:browsernpm run build:test && npm run unit-test:browser && npm run integration-test:browser
  • test:nodenpm run build:test && npm run unit-test:node && npm run integration-test:node
  • unit-testnpm run unit-test:node && npm run unit-test:browser
  • unit-test:browserkarma start --single-run
  • unit-test:nodemocha -r esm --require ts-node/register --reporter ../../../common/tools/mocha-multi-reporter.js --timeout 1200000 --full-trace "test/{,!(browser)/**/}/*.spec.ts"
Dependencies5
  • @azure/core-auth^1.3.0
  • @azure/core-http^1.2.0
  • @azure/core-tracing1.0.0-preview.11
  • @azure/logger^1.0.0
  • tslib^2.2.0