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
- 19,339Mainstream · −50% score
- Versions published
- 1,371Mature · −50% score
- First published
- Sep 2021
- Publisher
- imodeljs
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 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":["@itwin/[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":["@itwin/[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
Scripts11
buildnpm run -s build:cjs && npm run -s build:esmbuild:cjstsc 1>&2 --outDir lib/cjsbuild:esmtsc 1>&2 --module ES2022 --outDir lib/esmcleanrimraf -g lib .rush/temp/package-deps*.jsoncovernpm -s testdocsbetools docs --json=../../generated-docs/core/webgl-compatibility/file.json --tsIndexFile=./webgl-compatibility.ts --onlyJsonextract-apibetools extract-api --entry=webgl-compatibilitylinteslint "./src/**/*.ts" 1>&2lint-deprecationeslint --fix -f visualstudio --no-inline-config -c ../../common/config/eslint/eslint.config.deprecation-policy.js "./src/**/*.ts"testnpm run -s webpackTests && certa -r chromewebpackTestswebpack --config ./src/test/utils/webpack.config.js 1>&2
Dependencies1
@itwin/core-bentley5.11.0-dev.10