Skip to content
ContractSpec
Start here

Package manual · integrations

·Integrations and provider selection

integration.providers-impls

Integration provider implementations for email, payments, storage, and more

integrationsintegrationv7.0.5stableservernode
@lssm-tech/integration.providers-impls
bun add @lssm-tech/integration.providers-impls
Package source ↗Manifest ↗

Manifest declarations describe the current workspace; they do not verify registry publication or runtime execution.

Package guide

Website: https://contractspec.io

Compatibility facade and all-provider factory for ContractSpec provider implementations.

What It Provides

  • Layer: integration.
  • Consumers: bundles, apps, and modules that still need the broad compatibility surface or the all-provider factory.
  • Targeted provider implementation packages now own the concrete domains, such as @lssm-tech/integration.provider-email, @lssm-tech/integration.provider-payments, @lssm-tech/integration.provider-voice, and @lssm-tech/integration.provider-project-management.
  • Governed scraping, research, browser automation, and residential proxy adapters are canonical in @lssm-tech/integration.provider-web-access and re-exported from ./web-access.
  • Related ContractSpec packages include @lssm-tech/integration.runtime, @lssm-tech/lib.contracts-integrations, @lssm-tech/lib.contracts-spec, @lssm-tech/tool.bun, and @lssm-tech/tool.typescript.

Installation

npm install @lssm-tech/integration.providers-impls

or

bun add @lssm-tech/integration.providers-impls

Usage

Prefer a targeted package when you only need one provider domain:

ts
import { GmailInboundProvider } from '@lssm-tech/integration.provider-email/impls/gmail-inbound';
import { StripePaymentsProvider } from '@lssm-tech/integration.provider-payments/impls/stripe-payments';
import { TavilyAdapter } from '@lssm-tech/integration.provider-web-access';

Existing imports from @lssm-tech/integration.providers-impls and its ./impls/* subpaths remain supported as compatibility re-exports. Keep using this package for IntegrationProviderFactory or when you intentionally need the broad composition surface.

FullEnrich remains canonical in this package until the repository integration dependency-governance source rule explicitly permits the aggregator-to-provider edge. This defers only physical extraction: the API, secret-reference factory, webhook helpers, error normalization, and hosted-MCP descriptor remain available from ./impls/fullenrich-sales-intelligence*.

Communication Coverage

IntegrationProviderFactory now covers the main OSS communication paths directly:

  • createEmailInboundProvider(...) for Gmail thread/message sync
  • createEmailOutboundProvider(...) for Gmail and Postmark delivery
  • createSmsProvider(...) for Twilio SMS
  • createMessagingProvider(...) for Telegram, WhatsApp Meta, and WhatsApp Twilio

Architecture

  • src/analytics.ts, src/calendar.ts, src/database.ts, src/email.ts, src/embedding.ts, and the other domain files are compatibility re-exports to targeted packages.
  • src/impls/provider-factory.ts owns the all-provider factory and imports targeted packages.
  • src/impls/composio-* owns the cross-domain Composio fallback/proxy surface.
  • src/impls/* provider implementation files are compatibility re-exports to targeted packages.
  • src/index.ts is the root public barrel and package entrypoint.

Targeted Packages

  • @lssm-tech/integration.provider-analytics
  • @lssm-tech/integration.provider-calendar
  • @lssm-tech/integration.provider-database
  • @lssm-tech/integration.provider-email
  • @lssm-tech/integration.provider-embedding
  • @lssm-tech/integration.provider-health
  • @lssm-tech/integration.provider-llm
  • @lssm-tech/integration.provider-meeting-recorder
  • @lssm-tech/integration.provider-messaging
  • @lssm-tech/integration.provider-openbanking
  • @lssm-tech/integration.provider-payments
  • @lssm-tech/integration.provider-project-management
  • @lssm-tech/integration.provider-instagram
  • @lssm-tech/integration.provider-sms
  • @lssm-tech/integration.provider-storage
  • @lssm-tech/integration.provider-tiktok
  • @lssm-tech/integration.provider-vector-store
  • @lssm-tech/integration.provider-voice
  • @lssm-tech/integration.provider-web-access
  • @lssm-tech/integration.provider-x
  • @lssm-tech/integration.provider-youtube

Social providers

The social provider facade exposes namespaced social.youtube, social.tiktok, social.instagram, and social.x targeted packages. They support only accounts that explicitly connect through official APIs; they do not provide scraping, cookie authentication, unapproved public-account discovery, or write effects. Vendor MCP is unavailable until a provider documents an endpoint and an integrator configures its authenticated connection.

createOfficialSocialTrackingSources composes the four official tracking adapters with opaque credential resolvers. Applications can pass those sources to the social tracking runtime, then add an approved connector or the runtime's tenant-opt-in public metadata source without coupling provider packages to one another.

Public Entry Points

  • Export . resolves through ./src/index.ts.
  • Export ./analytics resolves through ./src/analytics.ts.
  • Export ./calendar resolves through ./src/calendar.ts.
  • Export ./database resolves through ./src/database.ts.
  • Export ./email resolves through ./src/email.ts.
  • Export ./embedding resolves through ./src/embedding.ts.
  • Export ./health resolves through ./src/health.ts.
  • Export ./web-access resolves through ./src/web-access.ts and remains a compatibility re-export of the targeted web-access package.
  • Export ./impls resolves through ./src/impls/index.ts.
  • Export ./impls/pioneer-ai resolves through ./src/impls/pioneer-ai.ts.
  • Export ./impls/slng-voice resolves through ./src/impls/slng-voice.ts.
  • Export ./impls/async-event-queue resolves through ./src/impls/async-event-queue.ts.
  • Export ./impls/composio-fallback-resolver resolves through ./src/impls/composio-fallback-resolver.ts.
  • The package publishes 81 total export subpaths; keep docs aligned with package.json.

Local Commands

  • bun run dev — contractspec-bun-build dev
  • bun run build — contractspec-bun-build build
  • bun run test — bun test
  • bun run lint — bun lint:fix
  • bun run lint:check — biome check .
  • bun run lint:fix — biome check --write --unsafe --only=nursery/useSortedClasses . && biome check --write .
  • bun run typecheck — tsgo --noEmit
  • bun run publish:pkg — bun publish --tolerate-republish --ignore-scripts --verbose
  • bun run publish:pkg:canary — bun publish:pkg --tag canary
  • bun run clean — rimraf dist .turbo
  • bun run build:bundle — contractspec-bun-build transpile
  • bun run build:types — contractspec-bun-build types
  • bun run prebuild — contractspec-bun-build prebuild

Recent Updates

  • Missing dependencies (thanks to knip).
  • Replace eslint+prettier by biomejs to optimize speed.
  • Resolve lint, build, and type errors across nine packages.
  • Resolve lint, build, and test failures across voice, workspace, library, and composio.
  • Composio.
  • Normalize formatting across contracts-integrations, composio, and observability.

Notes

  • Every implementation must satisfy a contract from contracts-integrations.
  • Never import from apps or bundles.
  • Secrets must flow through @lssm-tech/integration.runtime; never hard-code credentials.
  • Composio fallback is opt-in; existing code paths are unchanged when config is absent.
  • Composio proxy adapters must not leak Composio-specific types into domain interfaces.
  • @lssm-tech/integration.provider-pioneer-ai for mock-first Pioneer AI self-improvement job/evaluation integration.

Sales intelligence compatibility adapters

  • ./impls/fullenrich-sales-intelligence exports a mockable FullEnrich adapter for credits, API-key validation, search, lookup, async enrichment starts, webhook normalization, and remote MCP metadata. The adapter accepts an injected transport so tests never call live provider APIs and redacts API keys, tokens, emails, and phone-like fields from normalized output.
  • ./impls/sillage-sales-intelligence exports a fail-closed Sillage adapter that returns/throws SILLAGE_VENDOR_DOCS_REQUIRED. It performs no network call until official vendor docs or confirmed schemas are available.

The @lssm-tech/integration.providers-impls/builder-execution entry collects the existing Codex and OpenCode Go execution constants, preflight checks, and receipt constructors. It forwards the canonical provider implementations and leaves execution settings and approval policy with the caller.

Relationships

THIS PACKAGEintegration.providers-impls99 import paths

Arrows point from a package to its direct dependency. Counts are derived from captured workspace manifests.

32 declarations

Declared capabilities

Integration Providers Impls

Integration provider implementations for email, payments, storage, and more

Builder execution provider collection

Collect the existing canonical Codex and OpenCode Go execution adapters without changing execution policy.

Scripts

  • publish:pkgbun publish --tolerate-republish --ignore-scripts --verbose
  • publish:pkg:canarybun publish:pkg --tag canary
  • buildcontractspec-bun-build build
  • build:bundlecontractspec-bun-build transpile
  • build:typescontractspec-bun-build types
  • devcontractspec-bun-build dev
  • cleanrimraf dist .turbo
  • lintbun lint:fix
  • lint:fixnode ../../../scripts/biome.cjs check --write --unsafe --only=nursery/useSortedClasses . && node ../../../scripts/biome.cjs check --write .
  • lint:checknode ../../../scripts/biome.cjs check .
  • testbun test
  • prebuildcontractspec-bun-build prebuild
  • typechecktsgo --noEmit