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
- 125
- Versions published
- 16Established · −30% score
- First published
- Oct 2022
- Publisher
- uladkasach
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":["[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":["[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
Scripts28
buildnpm run build:clean && npm run build:compilebuild:cleanrm dist/ -rfbuild:compiletsc -p ./tsconfig.build.jsonbuild:tstsc -p ./tsconfig.build.jsoncommit:with-clinpx czfixnpm run fix:format && npm run fix:lintfix:formatnpm run fix:format:biomefix:format:biomebiome check --write srcfix:lintbiome check --write srcpostversiongit push origin HEAD --tags --no-verifyprepare[ -d .git ] && npm run prepare:husky || exit 0prepare:huskynpx husky install && chmod ug+x .husky/*prepublishnpm run buildprepushnpm run test && npm run buildpreversionnpm run prepushtestnpm run test:commits && npm run test:types && npm run test:format && npm run test:lint && npm run test:unit && npm run test:integration && npm run test:acceptance:locallytest:acceptancenpm run build && jest -c ./jest.acceptance.config.ts --forceExit --verbose --runInBand --passWithNoTeststest:acceptance:locallynpm run build && LOCALLY=true jest -c ./jest.acceptance.config.ts --forceExit --verbose --runInBand --passWithNoTeststest:commitsLAST_TAG=$(git describe --tags --abbrev=0 @^ 2> /dev/null || git rev-list --max-parents=0 HEAD) && npx commitlint --from $LAST_TAG --to HEAD --verbosetest:formatnpm run test:format:biometest:format:biomebiome format srctest:integrationjest -c ./jest.integration.config.ts --forceExit --verbose --passWithNoTests $([ -z $THOROUGH ] && echo '--changedSince=main')test:lintnpm run test:lint:biome && npm run test:lint:depstest:lint:biomebiome check src --diagnostic-level=errortest:lint:biome:allbiome check srctest:lint:depsnpx depcheck -c ./.depcheckrc.ymltest:typestsc -p ./tsconfig.json --noEmittest:unitjest -c ./jest.unit.config.ts --forceExit --verbose --passWithNoTests $([ -z $THOROUGH ] && echo '--changedSince=main')
Dependencies9
@aws-sdk/client-s3^3.887.0@ehmpathy/uni-time^1.4.0bottleneck^2.19.5domain-objects0.31.0hash-fns^1.1.0helpful-errors1.5.3serde-fns^1.2.0simple-in-memory-cache^0.4.0type-fns1.21.0