PkgRadar

Package evidence

@kong-ui-public/[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
1,056Mature · −50% score
First published
Jan 2025
Publisher
GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: 70% (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.

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":["@kong-ui-public/[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":["@kong-ui-public/[email protected]"],"fail_on":"review"}'
Artifact bytes115,345
Previous version1.15.20-pr.3398.62160fa19.0
Published2026-06-12T07:35:59.371Z
SHA-2566b0357b4adb27c848339c5fbbeb47e1c7a59ff228a66cf16e44d426ef505f28c

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
Last checked
reviewRisk
3Score
1.15.20-pr.3398.894c01e6e.0Version
Status history (1 event)
  1. newavailable · risk review · score 3 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/dist/entities-redis-configurations.es.jsmatched "aws_access_key"5
lowCredential file accesspackage/dist/entities-redis-configurations.umd.jsmatched "aws_access_key"5

Manifest

Package metadata

Scripts16
  • buildrun-s typecheck build:package build:types
  • build:analyzerBUILD_VISUALIZER='entities/entities-redis-configurations' vite build -m production
  • build:packagevite build -m production
  • build:sandboxcross-env USE_SANDBOX=true vite build -m production
  • build:typesvue-tsc -p './tsconfig.build.json' --emitDeclarationOnly
  • devcross-env USE_SANDBOX=true vite
  • linteslint
  • lint:fixeslint --fix
  • previewcross-env USE_SANDBOX=true vite preview
  • stylelintstylelint --allow-empty-input './src/**/*.{css,scss,sass,less,styl,vue}'
  • stylelint:fixstylelint --allow-empty-input './src/**/*.{css,scss,sass,less,styl,vue}' --fix
  • test:componentBABEL_ENV=cypress cross-env FORCE_COLOR=1 cypress run --component -b chrome --spec './src/**/*.cy.ts' --project '../../../.'
  • test:component:openBABEL_ENV=cypress cross-env FORCE_COLOR=1 cypress open --component -b chrome --project '../../../.'
  • test:unitcross-env FORCE_COLOR=1 vitest run
  • test:unit:opencross-env FORCE_COLOR=1 vitest --ui
  • typecheckvue-tsc -p './tsconfig.build.json' --noEmit
Dependencies3
  • @kong-ui-public/entities-plugins-icon^1.6.6
  • lodash-es>=4.18.0
  • uuid^14.0.0