PkgRadar

Package evidence

@openfeature/[email protected]

no findings

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
18Established · −30% score
First published
Dec 2023
Publisher
toddbaert

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

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":["@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 bytes482,471
Previous version0.2.3
Published2025-05-27T21:57:22.229Z
SHA-2562124d57732ad9f21369e432f12e62b0a3361dbf348d6efff127725e5187fc7aa

Why flagged

What the scanner saw

No high-signal static finding in the saved report.

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.4Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts12
  • buildnpm run clean && npm run build:esm && npm run build:cjs && npm run build:rollup-types
  • build:cjsesbuild src/index.ts --bundle --external:@nestjs/* --external:@openfeature/server-sdk --sourcemap --target=es2015 --platform=node --format=cjs --outfile=./dist/cjs/index.js --analyze
  • build:esmesbuild src/index.ts --bundle --external:@nestjs/* --external:@openfeature/server-sdk --sourcemap --target=es2015 --platform=node --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 ./
  • lint:fixeslint ./ --fix
  • 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