integrationPackage manifestv7.0.5

integration.providers-impls

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

@lssm-tech/integration.providers-impls
Source, release and verification context

Source snapshot bcc79fcc · Declared package version 7.0.5. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.

Package source ↗ Manifest ↗
servernode
EXPLORE THE PACKAGE

See where this package fits.

Follow a declared connection, inspect an import, then open the source guide when you need the detail.

THIS PACKAGEintegration.providers-implsintegrations

Arrows point from a package to its direct dependency. Each count is derived from the captured manifests.

32 déclarations · les 6 premières affichéesSELECT TO INSPECT

@lssm-tech/integration.providers-impls

Website: https://contractspec.io

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

What It Provides

  • Couche: 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.

Declared capabilities.

Integration Providers Impls

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

Use it to

  • Adopt integration provider implementations for email, payments, storage, and more

Requires

  • TypeScript

Choose another boundary when

  • The @lssm-tech/integration.providers-impls package constraints do not match the target runtime or platform.

@lssm-tech/integration.providers-impls

@lssm-tech/integration.providers-impls/analytics

@lssm-tech/integration.providers-impls/calendar

@lssm-tech/integration.providers-impls/database

@lssm-tech/integration.providers-impls/email

@lssm-tech/integration.providers-impls/embedding

@lssm-tech/integration.providers-impls/health

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

@lssm-tech/integration.providers-impls/impls/async-event-queue

@lssm-tech/integration.providers-impls/impls/composio-fallback-resolver

@lssm-tech/integration.providers-impls/impls/composio-mcp

@lssm-tech/integration.providers-impls/impls/composio-proxies

Builder execution provider collection

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

Use it to

  • Compose existing Builder execution provider adapters through their canonical collection.

Requires

  • TypeScript

Choose another boundary when

  • An execution provider other than the existing Codex and OpenCode Go adapters is required.

@lssm-tech/integration.providers-impls/builder-executionCODEX_FRONTIER_MODEL, CODEX_PROVIDER_ID, createCodexExecutionReceipt, preflightCodexSubscription, createOpenCodeGoExecutionReceipt, OPENCODE_GO_DEFAULT_MODEL, preflightOpenCodeGo

Imports and export paths.

99 entries

These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.

99 imports · 35 affichés

Dependencies and related packages.

Runtime dependencies 32
zod
catalog:
Peer dependencies 17
@composio/core
catalog:integrations
@confiture-ai/gradium-sdk-js
catalog:integrations
@elevenlabs/elevenlabs-js
^2.68.0
@fal-ai/client
catalog:integrations
@google-cloud/storage
^8.2.0
@linear/sdk
catalog:integrations
@mistralai/mistralai
^2.7.0
@notionhq/client
catalog:integrations
@qdrant/js-client-rest
^1.17.0
drizzle-orm
^0.45.2
fathom-typescript
catalog:integrations
googleapis
catalog:integrations
postgres
^3.4.9
posthog-node
^5.51.7
postmark
^4.0.7 || ^5.1.0
stripe
^22.6.2
twilio
catalog:integrations
Development dependencies 5
@composio/core
catalog:integrations
@types/bun
catalog:types
typescript
catalog:

Package scripts.

Commands declared by this package. Review its setup requirements before running them; no command here was executed by this review.

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
Votre vue

Make room for your context.

Shape the presentation around this moment. You can change it whenever you need.

Votre contexte

The different parts of you

Choose a starting point

Un mélange utile de contexte, de visuels et de guidage discret.

Tune each dimension
Each dimension can change independently. Product permissions and available actions stay unchanged.

Support the way you begin and return

Tune your support

Confort de lecture

Choisir votre langue

La langue de l’interface change uniquement le texte. Les marchés, les prix et les parcours conservent leurs propres paramètres.

Couverture des traductions

Une partie du contenu est affichée en anglais.

Navigation151
Graphe616
Catégories378
Portfolio833
Exemples2 035
Aperçu de la source1 542

D’autres traductions seront ajoutées à mesure que le contenu sera relu.

Cette préférence est enregistrée dans ce navigateur.

Rechercher sur le site

Des points de départ utiles

Aucun résultat. Essayez une expression plus courte, un nom d’opération ou un autre périmètre de recherche.

UN PEU DE PLACE POUR EXPLORER

Trouvez quelque chose à explorer.

Ouvrez un aperçu détaillé sur cette page, essayez une autre perspective ou suivez le détail vers sa propre page.

Fonctionnement des aperçus et des commandes
01

Regarder avant de partir

Survolez un lien ou sélectionnez-le avec Tab pour voir un aperçu. Cliquer sur le lien d’origine ou appuyer sur Entrée ouvre toujours sa destination.

02

Rester dans le contexte

Entrez dans l’aperçu pour explorer ses sections. Depuis un lien sélectionné, utilisez Alt + ↓ pour y entrer au clavier. Échap le ferme.

03

Ouvrir les possibilités

Les lignes dépliables, les choix de perspective et les commandes mises en évidence révèlent davantage. Votre vue adapte le confort de lecture et le contexte exploré.

Un bouton séparé pour voir de plus près

Affichez de petits boutons d’aperçu à côté des liens quand l’espace le permet. Touchez l’œil pour examiner ou le lien pour y aller directement. Ce choix reste dans cet onglet.

Aucun historique de navigation n’est collecté. La réduction des animations suit votre appareil et Votre vue.