Resource-scan receipts

traccar/traccar

Canonical URL: https://github.com/traccar/traccar · Fetched from: https://raw.githubusercontent.com/traccar/traccar/HEAD/README.md · Machine form: /v1/resource-scans/github-com-traccar-traccar-ef62c44a03 · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 1596e06c59c2054f7d9a25f7e2eca6264216159fd1b359fee03397ee5bbe5d7a · 2467 bytes · scanned 2026-11-12T02:42:43.856Z · scanner resource-scan-v1 · ledger entry 36059.

The rightshold on https://github.com/traccar/traccar — scanned 2026-11-12 · 3 of 8 checks flagged · receipt rsc_0f6c4a38db08a1b19e7c113b, verify at rightshold.com/verify.

Analysis is static only: the bytes were read as text and were never executed, installed or run. Nothing was fetched from behind a login.

Checks (latest receipt)

• Outbound network references — flag

  The scanned bytes reference outbound network activity to these domains: github.com, raw.githubusercontent.com, www.traccar.org. Any resource that reaches the network can send data out as well as bring data in; the findings name what the bytes reference, and the reader decides whether that fits the resource's stated purpose.

  Evidence: domain: github.com; domain: raw.githubusercontent.com; domain: www.traccar.org

• Credential and environment access — pass

  No credential or environment access patterns were found in the scanned bytes.

• Install and postinstall hooks — pass

  No install or postinstall hooks were found in the scanned bytes.

• Obfuscation and encoded payloads — pass

  No obfuscation or encoded-payload signs were found in the scanned bytes.

• Shell-outs and download-and-execute — flag

  The scanned bytes contain shell-out or download patterns: shell command tools named in the bytes (curl, wget, powershell). Code that runs shell commands acts with the full permissions of whoever runs it.

  Evidence: shell command tools named in the bytes (curl, wget, powershell)

• Permission declarations vs behavior — flag

  The bytes show network behavior, and no permissions declaration was found in the scanned bytes to compare it against.

  Evidence: behavior: network

• Known-bad indicators — pass

  None of the scanner's published known-bad indicator patterns matched the scanned bytes.

• Provenance facts (weak signals) — pass

  Provenance facts, labeled weak signals — they say where the bytes sit, not what the bytes do: source host: github.com; repository: traccar/traccar; bytes scanned: 2467; fetched from: https://raw.githubusercontent.com/traccar/traccar/HEAD/README.md.

  Evidence: source host: github.com; repository: traccar/traccar; bytes scanned: 2467; fetched from: https://raw.githubusercontent.com/traccar/traccar/HEAD/README.md

History

Every receipt for this artifact so far names the same SHA-256: the bytes have not changed between scans.

• 2026-11-12 — 3 of 8 checks flagged · SHA-256 1596e06c59c2054f… · 2467 bytes · scanner resource-scan-v1 · ledger entry 36059