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
- 115Mature · −50% score
- First published
- Apr 2020
- Publisher
- dirkjanfaber
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 monitoringNo 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":["@victronenergy/[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":["@victronenergy/[email protected]"],"fail_on":"review"}'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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts12
buildrollup -cbuild:testrollup -c rollup.test.config.mjsdocumentationbash -c '( sed "/^<!--/q" src/nodes/config-client.html && node scripts/service2doc.js -s src/services/services.json -r src/nodes/victron-nodes.html -o nodered ) | sponge src/nodes/config-client.html'lintstandard --fix src/ scripts/preparehusky || echo "WARNING: husky not available, proceeding"prereleasenpm run verifyreleasegit tag -d v$npm_package_version; git tag v$npm_package_version && git push --tags && git push && npm run create-releasetestnpm run lint && npm run build && npm run build:test && npm run test:unittest:coveragejest --coveragetest:unitjestverifynpm testwikibash -c 'S="src/services/services.json" R="src/nodes/victron-nodes.html"; node scripts/service2doc.js -s $S -r $R -o md --page index | sponge ../node-red-contrib-victron.wiki/Available-nodes.md && node scripts/service2doc.js -s $S -r $R -o md --page input | sponge ../node-red-contrib-victron.wiki/Input-nodes.md && node scripts/service2doc.js -s $S -r $R -o md --page output | sponge ../node-red-contrib-victron.wiki/Output-nodes.md && node scripts/service2doc.js -s $S -r $R -o md --page virtual | sponge ../node-red-contrib-victron.wiki/Virtual-devices.md && node scripts/service2doc.js -s $S -r $R -o md --page sidebar | sponge ../node-red-contrib-victron.wiki/_Sidebar.md'
Dependencies5
dbus-native-victron^0.4.5dbus-victron-virtual^0.1.34debug^4.4.0lodash^4.17.21promise-retry^2.0.1