Package evidence

flowfile==0.12.0

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: 47Mature · −50% score
First published: May 2025
Publisher: Edward van Eechoud

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":["flowfile==0.12.0"],"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":["flowfile==0.12.0"],"fail_on":"review"}'

PublisherEdward van Eechoud

Artifact bytes7,880,062

Previous versionnone

Published2026-06-12T07:24:40

SHA-2564db43ccc8835438ab5abd14c2b1581b8a06f0f055a24ccea230aa15ff4d6edb1

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

26h agoLast checked

reviewRisk

30Score

0.12.0Version

Status history (1 event)

new → available26h ago · risk review · score 30 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 12 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
low	Credential file access	flowfile-0.12.0/flowfile/flowfile/web/static/assets/api-BPUfa6gq.js	matched "aws_access_key"	5
low	Credential file access	flowfile-0.12.0/flowfile_core/flowfile_core/alembic/versions/001_initial_schema.py	matched "aws_access_key"	5
low	Credential file access	flowfile-0.12.0/flowfile_core/flowfile_core/database/models.py	matched "aws_access_key"	5
low	Credential file access	flowfile-0.12.0/flowfile_core/flowfile_core/flowfile/database_connection_manager/db_connections.py	matched "aws_secret_access_key"	5
low	Credential file access	flowfile-0.12.0/flowfile_core/flowfile_core/flowfile/flow_data_engine/cloud_storage_reader.py	matched "aws_access_key"	5
low	Credential file access	flowfile-0.12.0/flowfile_core/flowfile_core/routes/cloud_connections.py	matched "aws_secret_access_key"	5
low	Credential file access	flowfile-0.12.0/flowfile_core/flowfile_core/schemas/cloud_storage_schemas.py	matched "aws_access_key"	5
low	Credential file access	flowfile-0.12.0/flowfile_worker/flowfile_worker/external_sources/s3_source/models.py	matched "aws_access_key"	5
low	Credential file access	flowfile-0.12.0/shared/cloud_storage/storage_options.py	matched "aws_access_key"	5
low	Credential file access	flowfile-0.12.0/test_utils/s3/data_generator.py	matched "aws_access_key"	5
low	Credential file access	flowfile-0.12.0/test_utils/s3/demo_data_generator.py	matched "aws_access_key"	5
low	Credential file access	flowfile-0.12.0/test_utils/s3/fixtures.py	matched "aws_access_key"	5