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.

Versions published
105
First published
Feb 2026
Publisher
nexowatt

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":["[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"}'
Publishernexowatt
Artifact bytes6,392,256
Previous version0.8.11
Published2026-06-18T19:28:32.936Z
SHA-25655ef5559da2b677369a0b95a861c3628403066bd25df6ab19222ffe0efa23985

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.8.12Version
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

Scripts220
  • admin:buildnpm --prefix src-admin-tab run build
  • admin:installnpm --prefix src-admin-tab install
  • buildnpm run admin:build
  • build:adapter-helpersnpm run sync:ts-adapter-helpers
  • build:adapter-mirrorsnpm run sync:ts-adapter-mirrors
  • build:allnpm run build && npm run build:ts
  • build:backend-mirrorsnpm run sync:ts-backend-mirrors
  • build:ems-mirrorsnpm run sync:ts-ems-mirrors
  • build:energy-flow-mirrorsnpm run sync:ts-energy-flow-mirrors
  • build:frontend-mirrorsnpm run sync:ts-frontend-mirrors
  • build:runtime-executablesnpm run sync:ts-runtime-executables
  • build:script-mirrorsnode scripts/build-ts-script-mirrors.js
  • build:shadow-bridgesnpm run sync:ts-shadow-bridges
  • build:tsnpm run clean:ts && npm run sync:ts-runtime-executables && npm run sync:ts-main-helpers && npm run sync:ts-scripts && npm run sync:ts-frontend-mirrors && npm run sync:ts-adapter-mirrors && npm run sync:ts-backend-mirrors && npm run sync:ts-adapter-helpers && npm run sync:ts-energy-flow-mirrors && npm run sync:ts-ems-mirrors && npm run sync:ts-shadow-bridges && npm run build:types
  • build:ts-runtime-teststsc -p tsconfig.test-runtime.json
  • build:ts-scriptsnpm run sync:ts-scripts
  • build:typestsc -p tsconfig.build.json
  • bump:majornode scripts/bump-version.js major
  • bump:minornode scripts/bump-version.js minor
  • bump:patchnode scripts/bump-version.js patch
  • check:conflictsnpm run git:conflicts
  • check:frontend-mirrorsnpm run check:ts-frontend-mirrors
  • check:ts-adapter-helpersnode scripts/build-ts-adapter-helpers.js --check
  • check:ts-adapter-mirrorsnpm run check:ts-adapter-helpers
  • check:ts-backend-mirrorsnode scripts/build-ts-backend-mirrors.js --check
  • check:ts-canonicalnode scripts/verify-ts-canonical-structure.js
  • check:ts-ems-mirrorsnode scripts/build-ts-ems-mirrors.js --check
  • check:ts-energy-flow-mirrorsnode scripts/build-ts-energy-flow-mirrors.js --check
  • check:ts-frontendnpm run check:ts-frontend-mirrors
  • check:ts-frontend-mirrorsnode scripts/build-ts-frontend-mirrors.js --check
  • …and 190 more.
Dependencies3
  • @iobroker/adapter-core^3.4.1
  • @iobroker/type-detector5.0.10
  • express^4.22.2