@lssm/bundle.osint
v2.0.2
Published
Composable OSINT provider routing and operator view models
Downloads
75
Readme
@lssm/bundle.osint
Reusable composition for all supported web-access providers and OSINT operator view models. Explicit provider plans can use Serper search, Linkup or Tavily deep research, Bright Data or Massive collection/proxy methods, and Browserbase rendered sessions. API, SDK, MCP, webhook, WebSocket/SSE, browser, and proxy capabilities remain visible in provenance rather than being flattened away. Each router is pinned to one deployment, credential namespace, and provider allowlist; bounded requests persist evidence before distinct-provider corroboration. Reusable controllers, hooks, and responsive design-system screens cover loading, empty, ready, degraded, unauthorized, conflict, stale, review, and evidence states.
Operator command center
normalizeOsintCommandCenterResultV1 projects untrusted service responses into
deduplicated, redacted records. It exposes only operational metadata needed for
source health, acquisition, evidence, freshness, recovery, and review; unknown
fields such as credentials, tokens, cookies, and personal payloads never enter
the view model. Partial-provider health remains an explicit presentation state.
Mutations are rendered only from a server-returned action descriptor containing an exact operation, immutable input, authorization reference, and idempotency key. The reusable coordinator enforces an optional exact confirmation phrase and coalesces concurrent invocations with the same idempotency key. The host may further narrow operations for a route, but it never constructs an action or decides whether an effect is allowed.
