PkgRadar

Package evidence

@openfeature/[email protected]

Credential file access: matched ".npmrc"

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
258,249Ubiquitous · −70% score
Versions published
39Mature · −50% score
First published
Sep 2023
Publisher
toddbaert

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

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

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":["@openfeature/[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":["@openfeature/[email protected]"],"fail_on":"review"}'
Publishertoddbaert
Artifact bytes119,424
Previous version0.2.0-experimental
Published2024-03-05T21:44:00.092Z
SHA-2568bdd7f0d8d9f7e38a54c7ddd4a97c44151db105578faacb86c30a9bbdb6c4e05

Why flagged

What the scanner saw

Credential file access: matched ".npmrc"

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

Availability ledger

available

low
Last checked
lowRisk
0Score
0.2.1-experimentalVersion
Status history (1 event)
  1. newavailable · risk low · score 0 · 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)
SeverityKindPathDetailPoints
lowCredential file accesspackage/package.jsonmatched ".npmrc"3

Manifest

Package metadata

Scripts11
  • buildnpm run clean && npm run build:react-esm && npm run build:react-cjs && npm run build:rollup-types
  • build:react-cjsesbuild src/index.ts --bundle --external:react --external:@openfeature/web-sdk --sourcemap --target=es2022 --platform=browser --format=cjs --outfile=./dist/cjs/index.js --analyze
  • build:react-esmesbuild src/index.ts --bundle --external:react --external:@openfeature/web-sdk --sourcemap --target=es2022 --platform=browser --format=esm --outfile=./dist/esm/index.js --analyze
  • build:rollup-typesrollup -c ../../rollup.config.mjs
  • cleanshx rm -rf ./dist
  • current-versionecho $npm_package_version
  • linteslint ./
  • postbuildshx cp ./../../package.esm.json ./dist/esm/package.json
  • prepackshx cp ./../../LICENSE ./LICENSE
  • publish-if-not-existscp $NPM_CONFIG_USERCONFIG .npmrc && if [ "$(npm show $npm_package_name@$npm_package_version version)" = "$(npm run current-version -s)" ]; then echo 'already published, skipping'; else npm publish --access public; fi
  • testjest --verbose