PkgRadar

Package evidence

[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
89
Versions published
123Mature · −50% score
First published
Sep 2024
Publisher
superflows-dev

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.

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":["[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":["[email protected]"],"fail_on":"review"}'
Artifact bytes240,656
Previous version1.0.123
Published2026-02-18T10:08:24.362Z
SHA-256018004072c2477517ee0704fcf13cf0cad791213b8079acd94ef9510a7e75da0

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
1.0.124Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts17
  • analyzecem analyze --litelement --globs "src/**/*.ts"
  • analyze:watchcem analyze --litelement --globs "src/**/*.ts" --watch
  • buildtsc
  • build:watchtsc --watch
  • checksizerollup -c ; cat sf-i-reporting.bundled.js | gzip -9 | wc -c ; rm sf-i-reporting.bundled.js
  • cleanrimraf sf-i-reporting.{d.ts,d.ts.map,js,js.map} test/sf-i-reporting.{d.ts,d.ts.map,js,js.map} test/sf-i-reporting_test.{d.ts,d.ts.map,js,js.map}
  • formatprettier "**/*.{cjs,html,js,json,md,ts}" --ignore-path ./.eslintignore --write
  • lintnpm run lint:lit-analyzer && npm run lint:eslint
  • lint:eslinteslint 'src/*.ts'
  • lint:lit-analyzerlit-analyzer
  • servewds --watch
  • serve:prodMODE=prod npm run serve
  • testnpm run test:dev && npm run test:prod
  • test:devwtr --verbose=true --coverage --silent=false
  • test:prodMODE=prod wtr
  • test:prod:watchMODE=prod wtr --watch
  • test:watchwtr --watch
Dependencies10
  • fs^0.0.1-security
  • lit^2.8.0
  • sf-checklist^1.0.17
  • sf-i-bricks^1.0.10
  • sf-i-elastic-text^1.0.17
  • sf-i-form^1.0.188
  • sf-i-select^1.0.93
  • sf-i-sub-select^1.0.83
  • sf-i-uploader^1.0.119
  • sinon^15.0.1