PkgRadar

Package evidence

@qrvey/[email protected]

Credential file access: matched "AWS_SECRET_ACCESS_KEY"

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
22Mature · −50% score
First published
Jul 2024
Publisher
qrvey-jespinel

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

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

Inspect tarballAdd to CI gate
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":["@qrvey/[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":["@qrvey/[email protected]"],"fail_on":"review"}'
Publisherqrvey-jespinel
Artifact bytes63,137
Previous version1.1.4-920
Published2026-03-25T13:54:49.216Z
SHA-25601efbafca0b4f1fb2df7c34267fa5e2ebf3d1f20de0de98eb13d3cf4eb9aa3f7

Why flagged

What the scanner saw

Credential file access: matched "AWS_SECRET_ACCESS_KEY"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review
Last checked
reviewRisk
7Score
1.1.4-920-betaVersion
Status history (1 event)
  1. new → available · risk review · score 7 · status changed

Evidence

Static findings

3 static · 0 from release diff · showing high-signal first.

No high-signal findings — see all findings below.

Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/dist/cjs/lib/services/eventService/eventBridgeService.jsmatched "AWS_SECRET_ACCESS_KEY"5
lowCredential file accesspackage/dist/esm/index.mjsmatched "AWS_SECRET_ACCESS_KEY"5
lowCredential file accesspackage/src/lib/services/eventService/eventBridgeService.tsmatched "AWS_SECRET_ACCESS_KEY"5

Manifest

Package metadata

Scripts16
  • buildyarn build:clean && yarn build:compile
  • build:cleanrm -rf dist
  • build:compileyarn build:compile:cjs && yarn build:compile:esm && yarn build:compile:types
  • build:compile:cjstsc -b ./tsconfig.cjs.json
  • build:compile:cjs:originaltsup --config ./tsup.config.cjs.ts
  • build:compile:esmtsup --config ./tsup.config.esm.ts
  • build:compile:originaltsc -b ./tsconfig.cjs.json ./tsconfig.esm.json ./tsconfig.types.json
  • build:compile:typestsup --config ./tsup.config.types.ts
  • login-code-artifactaws codeartifact --profile manualqa login --tool npm --domain qrvey-npm --repository qrvey-npm
  • prepare-publishyarn install && yarn build
  • publish-codeartifactnpm publish --prefix dist --registry=https://qrvey-npm-459649773688.d.codeartifact.us-east-1.amazonaws.com/npm/qrvey-npm/
  • publish-packageyarn prepare-publish && npm publis --tag beta
  • publish-package-devyarn prepare-publish && yarn publish-codeartifact
  • testjest
  • test:covjest --coverage && chmod +x ./coverageReader.sh && sh ./coverageReader.sh
  • type-checktsc
Dependencies3
  • @qrvey/fetch1.1.4
  • nanoid3.3.8
  • polly-js1.8.3