registry / @hadoku/jobplatform-worker / 2.32.14

@hadoku/jobplatform-worker@2.32.14

Job listings aggregation and tracking dashboard - Worker package

AI Security Review

scanned 4d ago · by lpm-firewall-ai

The scanner's credential and network hits correspond to service credentials sent to Hadoku's mail-feed, identity, scraper and resume services. The relevant data flows are feature-specific and API-triggered, with mail reconciliation scoped to the configured mailbox owner; package.json contains no lifecycle scripts.

Static reason

No blocking static signals were detected.

Trigger

Authenticated API requests invoke the relevant worker routes; no install hook or automatic scheduled task was found.

Impact

No unrelated credential collection, unsolicited account action or other malicious behavior was identified.

Mechanism

The worker uses bound service credentials and service bindings for requests to its related Hadoku services. Mail reconciliation checks the caller and configured mailbox owner.

AI rationale

Network endpoints4

hadoku.me/contact/api/mailfeedscraper.hadoku.mehadoku.me/session/identity/resolveresume-api

Decision evidence

public snapshot

AI called this Clean at 94.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The package describes a job listings worker and exports its worker entry point; package.json contains no lifecycle scripts.
Mail-feed requests send HADOKU_SERVICE_KEY to the Hadoku mail-feed service, using a configurable base URL.
Scraper requests send HADOKU_SERVICE_KEY to a configurable scraper service; the default host is scraper.hadoku.me.
Mail reconciliation runs through a requested API route that resolves the caller and checks that caller against the configured mailbox owner.
Resume requests use the configured RESUME service binding and send job data to its resume-api service endpoint.

Evidence against

Behavioral surface

Source

Network

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 199 KB of source, external domains: hadoku.me, job-boards.greenhouse.io, jobs.ashbyhq.com, jobs.lever.co, scraper.hadoku.me

Source & flagged code

5 flagged

package.jsonView file

1{ "name": "@hadoku/jobplatform-worker", "version": "2.32.14", "description": "Job listings aggregation and tracking dashboard - Worker package", "license": "MIT", "type": "module", "repository": { "type": "git", "url": "git+https://github.com/WolffM/hadoku-jobplatform.git" }, "files": [ "dist", "migrations" ], "exports": { ".": { "types": "./dist/index.d.ts", "default": "./dist/index.js" } }, "peerDependencies": { "@hono/zod-openapi": ">=1.0.0", "@wolffm/worker-utils": ">=1.5.4", "hono": ">=4.6.0" } }

Low

Suspicious Lifecycle Evidence

The package describes a job listings worker and exports its worker entry point; package.json contains no lifecycle scripts.

package.jsonView on unpkg · L1

dist/index.jsView file

833const DEFAULT_BASE_URL$1 = "https://hadoku.me/contact/api/mailfeed"; function baseUrl$1(env) { return (env.MAILFEED_BASE_URL ?? DEFAULT_BASE_URL$1).replace(/\/$/, ""); } async function get(env, path) { const key = env.HADOKU_SERVICE_KEY; if (!key) return { error: "HADOKU_SERVICE_KEY is not bound — cannot read the

Low

Ai Review Evidence

Mail-feed requests send HADOKU_SERVICE_KEY to the Hadoku mail-feed service, using a configurable base URL.

Findings

1 Medium7 Low

MediumNetwork

LowHigh Entropy Strings

LowUrl Strings

LowSuspicious Lifecycle Evidencepackage.json

LowAi Review Evidencedist/index.js

Affected versions and remediation

This report applies to @hadoku/jobplatform-worker@2.32.14.

See all versions of @hadoku/jobplatform-worker for other recorded verdicts.

Review the evidence and your use of @hadoku/jobplatform-worker@2.32.14 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-11-01 09:51:57.914Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.