nenadzaric/skills-integrations-telegram-integration repository overview

⁠telegram-integration

Recovered first-party workflow connector. Compatible legacy ports and exact tool identity are retained; optional dry-run defaults off.

⁠Exact immutable image

docker pull --platform linux/amd64 docker.io/nenadzaric/skills-integrations-telegram-integration@sha256:d729bc2795bf1c71abdb16348c01247f78cb370f5716748a92e0c9244fc9531d

Index digest: sha256:a30f8febf781848eba8044f2a939415ae2603357a6932d7e8dd86c6249e2a343.

⁠Executable source and original notices

The immutable companion artifact contains telegram-integration/build-source/ (actual recovered executable source, Dockerfile, pinned dependencies, native fixture checks and safe workflow definitions), telegram-integration/notices/ (original baseline/dependency and installed runtime license/copyright payloads) and the image/source/proof hash index. Git development repositories are private; this public artifact provides the actual source instead. No customer configuration, credentials, generated TLS private keys or signed download URLs are included.

oras pull docker.io/nenadzaric/skills-integrations-telegram-integration@sha256:ac605f09ea6be2e175110555a7a256d837f311f88350c250c27451e24a78af65
sha256sum telegram-integration-source-notices.tar.gz

Expected archive SHA256: 0562618815fc004904b3c47cb280461b10f8e5039699e584d6131758e2ac1041. Extract and read telegram-integration/SOURCE-DELIVERY.txt and telegram-integration/notices/SOURCE-AND-NOTICES.json. Recipe/catalog delivery links and later release status can change without changing executable image bytes; the artifact preserves its build-source snapshot.

⁠Test scope and credentials

Positive and negative native tests used owned local mocks. Actual bounded private platform workflows ran the registered native dry-run and verified downloaded plan artifacts; these prove typed file flow and planning ONLY, not provider execution, permission or live account compatibility. No real provider requests, messages, tickets, pages or records were created. Production execution requires provider credentials with suitable scopes; bind through existing tenant secret references, never commit tokens or echo them in outputs.

cd telegram-integration/build-source
IMAGE=docker.io/nenadzaric/skills-integrations-telegram-integration@sha256:d729bc2795bf1c71abdb16348c01247f78cb370f5716748a92e0c9244fc9531d sh tests/native.sh

Owned tests use network-none containers and synthetic loopback services. They are not authorization to send to real providers. Planning does not simulate all provider behavior (notably Slack/Telegram sends/media and Airtable JQ/update/link semantics). Existing retry logic is not an exactly-once guarantee after ambiguous writes.

⁠License scope

Original baseline MIT notices and dependency licenses remain unchanged. Recovery/packaging changes follow the existing workflows Proprietary first-party policy; this delivery makes no new license grant. Supplemental installed notices accompany the image; this is not an exhaustive SBOM or bit-reproducible binary claim. Python base/runtime components and Go/vendor/CA components retain their respective original terms.