PkgRadar

Package evidence

@nfq/[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.

Weekly downloads
58
Versions published
89Mature · −50% score
First published
Aug 2021
Publisher
nfqdbt

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

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":["@nfq/[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":["@nfq/[email protected]"],"fail_on":"review"}'
Publishernfqdbt
Artifact bytes212,249
Previous version6.1.0-beta3
Published2025-04-16T07:41:14.256Z
SHA-256f80793d9b51a4eae162c7c816cb5ea419d86fb9bf5d56273acfb9a6576e0e0b2

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
7.0.0Version
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

Scripts9
  • buildpnpm cross-env NODE_ENV=production rollup -c && pnpm tsc
  • check:typespnpm tsc --noEmit
  • deploystandard-version && git push --follow-tags origin main && pnpm publish
  • lintpnpm eslint ./src --ext='.js' --ext='.jsx' --ext='.ts' --ext='.tsx'
  • lint:reportpnpm eslint --output-file eslint_report.json --format json --ext='.js, .jsx, .ts, .tsx' ./src
  • merge:filespnpm mochawesome-merge "./cypress/reports/mochawesome*.json" > "./cypress/reports/index.json"
  • testpnpm cross-env CYPRESS_INTERNAL_BROWSER_CONNECT_TIMEOUT=300000 NODE_ENV=test pnpm cypress run --component && pnpm merge:files
  • test:openpnpm cross-env NODE_ENV=test pnpm cypress open --component
  • watchpnpm cross-env NODE_ENV=dev rollup -c -w
Dependencies3
  • @emotion/react^11.14.0
  • @emotion/styled^11.14.0
  • uuid^11.1.0