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
- 126
- Versions published
- 10Established · −30% score
- First published
- Sep 2021
- Publisher
- ajivani007
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":["@mchp-mcc/[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":["@mchp-mcc/[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
Scripts19
buildgulp build --gulpfile config/gulpfile.js --cwd .build-devgulp build --gulpfile config/gulpfile.js --buildDev --cwd .build-latest-run-diryarn add @microchip/run-directory && node config/extract-run-directory.jsbuild-prodgulp build --gulpfile config/gulpfile.js --production --cwd .build-run-dirnode config/extract-run-directory.jscreate-auto-modulegulp create-auto-module --gulpfile config/gulpfile.js --cwd .distgulp dist --gulpfile config/gulpfile.js --cwd .linttsc --noEmit && yarn lint:nofix --fixlint:nofixeslint "./src/**/*.{ts,tsx}" --quietpostprocessnode config/appendPrototype.jsprofilejest profilereleaseyarn build && yarn test && node -e 'require("./config/scf-project-scripts").releaseProject()'startgulp start --gulpfile config/gulpfile.js --cwd .testjesttest:itf:allnode ./node_modules/@microchip/ccl-itf/lib/index.js --sp=./tests --rd=./run --sf=clkctrl_v3.major.test.ts --df="AVR64DB28|AVR32EA48|AVR32DD32|AVR16LA32|AVR32LA32"test:itf:devnode ./node_modules/@microchip/ccl-itf/lib/index.js --sp=./tests/itf --rd=./run --sf=clkctrl_v3.major.test.ts --df="AVR64DB28|AVR32LA32"test:itf:interfacenode ./node_modules/@mchp-mcc/ccl-itf/lib/index.js --sp=tests/itf --rd=run --intf=scf-avr8-clkctrl-v3 --intV=1.0.0update-auto-moduleyarn add @microchip/scf-automodule -D && yarn upgrade @microchip/melody-automodule-interface && yarn updateProjectupdateProjectnode config/create-auto-module.js --updateProject=true
Dependencies14
@mchp-mcc/avr-8bit^4.14.3-dev.9@microchip/api-prefix-registration^0.1.0@microchip/config-device^1.1.1@microchip/config-request^2.0.2@microchip/fosc-hz^0.1.2@microchip/interrupt-standard^1.0.1@microchip/osc-clocks^0.2.0@microchip/pins-interface^1.0.1@microchip/run-directory^4.6.0@microchip/scf-common^3.22.7@microchip/scf-device^8.11.1@microchip/scf-integration-test^1.0.0@microchip/scf-interface^1.4.0@microchip/scf-register-view-helper^2.8.1