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
- 7
- Versions published
- 4
- First published
- Jun 2024
- Publisher
- julianrojas87
Recommended action
Review before promotingMixed 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":["@rdfc/[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":["@rdfc/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Remote Payload: matched "wget "
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk review · score 12 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Remote Payload | package/lib/util.js | matched "wget " | 12 |
Manifest
Package metadata
Scripts4
buildtsc && tsc-aliasprepublishOnlynpm run buildtestvitest run --coverage --coverage.include srcwatchtsc -w
Dependencies9
@rdfc/js-runner^3.1.0@rdfjs/types^2.0.1@rmlio/yarrrml-parser^1.12.2@treecg/types^0.4.6n3^2.0.3rdf-data-factory^2.0.2rdf-lens^1.3.7rdf-stores^2.2.0winston^3.19.0