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,955Mature · −50% score
- First published
- Jan 2020
- Publisher
- aws-amplify-ops
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":["@aws-amplify/[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":["@aws-amplify/[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
Scripts13
buildnpm run clean && npm run build:esm && npm run build:cjsbuild-with-testnpm test && npm run buildbuild:cjsrimraf lib && tsc -m commonjs --outDir lib && webpack && webpack --config ./webpack.config.dev.jsbuild:cjs:watchrimraf lib && tsc -m commonjs --outDir lib --watchbuild:esmrimraf lib-esm && tsc -m esnext --outDir lib-esmbuild:esm:watchrimraf lib-esm && tsc -m esnext --outDir lib-esm --watchcleannpm run clean:size && rimraf lib-esm lib distclean:sizerimraf dual-publish-tmp tmp*formatecho "Not implemented"linttslint 'src/**/*.ts' && npm run ts-coveragetestnpm run lint && jest --coveragetest:sizesize-limitts-coveragetypescript-coverage-report -p ./tsconfig.build.json -t 65.41
Dependencies4
@aws-amplify/core5.8.16axios^1.16.1tslib^1.8.0url0.11.0