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
- 509
- Versions published
- 25
- First published
- Apr 2026
- Publisher
- luckyace35
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@awsless/[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":["@awsless/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched "AWS_ACCESS_KEY"
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 review · score 16 · status changed
Evidence
Static findings
4 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 4 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/dist/bin.js | matched "AWS_ACCESS_KEY" | 5 |
| low | Credential file access | package/dist/build-json-schema.js | matched ".aws" | 5 |
| low | Credential file access | package/dist/app.json | matched ".aws" | 3 |
| low | Credential file access | package/dist/stack.json | matched ".aws" | 3 |
Manifest
Package metadata
Scripts12
bermzsh -c 'pnpm build; pnpm build-features; pnpm build-json-schema; bun dist/bin.js ${*} --config-file=./test/_data/app.jsonc' --buildpnpm tsup src/bin.ts --format esm --dts --clean --external bunbuild-json-schemapnpm tsup cli/build-json-schema.ts --format esm; bun ./dist/build-json-schema.jsbuild-layersmkdir -p dist/layers && cp -r layers/* dist/layersbuild-prebuildpnpm tsup src/prebuild.ts --format esm; bun ./dist/prebuild.jsbuild-test-setuppnpm tsup src/test/test-global-setup.ts --format esmjackpnpm tsup ./example/jack/jack.ts --format esm --external bun; bun ./dist/jack.jskennedypnpm tsup ./example/kennedy/kennedy.ts --format esm --external bun; bun ./dist/kennedy.jsprepublishif pnpm test; then pnpm build; pnpm build-json-schema; pnpm build-test-setup; pnpm build-prebuild; pnpm build-layers; else exit; fipublish-docker-imagezsh ./cli/publish-fargate-image.shtermzsh -c 'bun dist/bin.js ${*} --config-file=./test/_data/app.jsonc' --testpnpm vitest
Dependencies81
@aws-sdk/client-cloudformation^3.369.0@aws-sdk/client-cloudfront^3.991.0@aws-sdk/client-cloudfront-keyvaluestore^3.817.0@aws-sdk/client-cloudwatch-logs^3.806.0@aws-sdk/client-cognito-identity-provider^3.840.0@aws-sdk/client-dynamodb3.363.0@aws-sdk/client-ecs^3.369.0@aws-sdk/client-lambda3.329.0@aws-sdk/client-route-53^3.782.0@aws-sdk/client-s3^3.369.0@aws-sdk/client-ssm3.329.0@aws-sdk/client-sts^3.369.0@aws-sdk/credential-providers^3.654.0@aws-sdk/lib-storage^3.423.0@aws-sdk/signature-v4-crt^3.816.0@awsless/big-float^0.1.6@awsless/cloudwatch^0.0.1@awsless/clui^0.0.8@awsless/duration^0.0.4@awsless/dynamodb^0.3.21@awsless/iot^0.0.5@awsless/json^0.0.11@awsless/lambda^0.0.44@awsless/redis^0.1.9@awsless/s3^0.0.21@awsless/scheduler^0.0.4@awsless/size^0.0.2@awsless/sns^0.0.10@awsless/sqs^0.0.22@awsless/ts-file-cache^0.0.16- …and 51 more.