Package evidence

@emuanalytics/[email protected]

Credential file access: matched "AWS_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: 54Mature · −50% score
First published: Jul 2023
Publisher: robin.summerhill

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 tarball Add 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":["@emuanalytics/[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":["@emuanalytics/[email protected]"],"fail_on":"review"}'

Publisherrobin.summerhill

Artifact bytes40,484

Previous version1.1.6

Published2026-06-09T12:45:46.410Z

SHA-256d7f444530609a6719dda99ab8bbb5a59f39e860477c06998a9194c5869f65b7e

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

review

4d agoLast checked

reviewRisk

1Score

1.1.7Version

Status history (1 event)

new → available4d ago · risk review · score 1 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 1 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
low	Credential file access	package/template-flow-pipelines-default/bitbucket-pipelines.yml	matched "AWS_ACCESS_KEY"	3

Manifest

Package metadata

Scripts9

buildunbuild
coveragevitest run --coverage
docker:buildpnpm --silent --workspace-root pnpm-context -p 'tsconfig*' -p 'vitest.config.ts' packages/example-pipeline/Dockerfile | docker build --build-arg PACKAGE_PATH=packages/example-pipeline - -t example-pipeline
docker:rundocker run -it -v $PWD/config/local-production.toml:/home/node/monorepo/packages/example-pipeline/config/local-production.toml example-pipeline
prepublishOnlypnpm run build
stamp-versionnode scripts/stamp-version.js ./src
starttsx src/index.ts
testvitest run
typechecktsc --noEmit -p tsconfig.check.json

Dependencies4

@emuanalytics/flow-engine-client^2.2.8
@emuanalytics/flow-pipelines^1.3.1
config^3.3.9
toml^3.0.0