Skills azure-eventhub-ts
📦
azure-eventhub-ts
Content revision r2 Medium Risk ⚙️ External commands🌐 Network access🔑 Env variables
Build Azure Event Hubs Workflows in TypeScript
Building reliable Event Hubs producers and consumers requires correct authentication, batching, partitioning, and checkpoint management. This skill provides focused TypeScript patterns for those tasks.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "azure-eventhub-ts" from https://skillstore.io/skills/sickn33-azure-eventhub-ts.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-eventhub-ts/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "azure-eventhub-ts". Plan a producer for ordered device telemetry.
Expected outcome:
- Use each device identifier as the partition key.
- Create bounded batches and verify every event fits before sending.
- Close the producer during graceful application shutdown.
Using "azure-eventhub-ts". Review a checkpointed consumer for duplicate processing risks.
Expected outcome:
- Treat delivery as at-least-once because events may replay after failures.
- Make downstream writes idempotent or deduplicate by a stable event identifier.
- Advance checkpoints only after successful processing.
Using "azure-eventhub-ts". Recommend safe consumer logging.
Expected outcome:
Log partition, offset, sequence number, event type, and a correlation identifier. Redact or omit complete event bodies.
Security Audit
Medium Riskv5 • 7/23/2026 Open versioned report
All 47 static findings are false positives caused by Markdown fences, TypeScript template literals, standard Azure endpoint construction, and non-secret resource configuration. Semantic review found that examples log complete event bodies and incorrectly describe checkpointing as exactly-once processing.
1
Files scanned
279
Lines analyzed
0
Review items
0
False positives ignored
Confirmed security concerns (2)
Medium
Complete Event Payloads Written to Logs
Consumer examples serialize complete event bodies to console output. Production payloads may contain credentials, personal data, or other sensitive information.
Both cited examples explicitly serialize event.body into logs. Exposure depends on the payload and production logging configuration.
Medium
Checkpointing Misrepresented as Exactly-Once Processing
The guidance claims checkpointing provides exactly-once processing. Replays remain possible, so non-idempotent handlers may repeat sensitive or costly side effects.
The exactly-once claim is explicit, while Event Hubs checkpoints track progress without making consumer side effects atomic.
Risk Factors
⚙️ External commands (40)
SKILL.md:15-17 SKILL.md:17-20 SKILL.md:20-22 SKILL.md:22-26 SKILL.md:26-31 SKILL.md:31-35 SKILL.md:35-53 SKILL.md:53-59 SKILL.md:59-69 SKILL.md:69-73 SKILL.md:73-79 SKILL.md:79-83 SKILL.md:83-89 SKILL.md:89-93 SKILL.md:93-102 SKILL.md:102-106 SKILL.md:106-112 SKILL.md:112-129 SKILL.md:129-137 SKILL.md:137-140 SKILL.md:140-144 SKILL.md:144-160 SKILL.md:160-164 SKILL.md:164-167 SKILL.md:167-171 SKILL.md:171-172 SKILL.md:172-176 SKILL.md:176-187 SKILL.md:187-191 SKILL.md:191-205 SKILL.md:205-209 SKILL.md:209-226 SKILL.md:226-227 SKILL.md:227-228 SKILL.md:228-229 SKILL.md:229-233 SKILL.md:233-237 SKILL.md:237-260 SKILL.md:260-265 SKILL.md:265-270
🌐 Network access (1)
🔑 Env variables (4)
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-azure-eventhub-ts/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-eventhub-ts?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-eventhub-ts?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-eventhub-ts/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-eventhub-ts.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). azure-eventhub-ts security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-eventhub-ts/audits/5BibTeX citation
@techreport{sickn33-sickn33-azure-eventhub-ts-2026,
author = {sickn33},
title = {azure-eventhub-ts security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-azure-eventhub-ts/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-eventhub-ts security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-azure-eventhub-ts/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-azure-eventhub-ts:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance
What You Can Build
Create a Telemetry Producer
Design a TypeScript producer that batches sensor events and preserves per-device ordering with partition keys.
Build a Checkpointed Consumer
Add Blob Storage checkpoints, consumer groups, error handling, and controlled shutdown to a stream processor.
Review Stream Processing Reliability
Assess batch settings, replay behavior, offsets, logging, and idempotency before a production release.
Try These Prompts
Create a Basic Producer
Create a TypeScript Event Hubs producer using DefaultAzureCredential. Batch three telemetry events, send them, and close the client.
Add a Consumer
Create a TypeScript consumer for [consumer group]. Process events from [event hub], handle errors, and shut down cleanly.
Configure Checkpointing
Extend my consumer with Azure Blob checkpointing. Explain required packages, resource settings, checkpoint timing, replay behavior, and failure handling.
Design a Production Pipeline
Design an Event Hubs pipeline for [workload]. Cover partition strategy, consumer groups, idempotency, checkpoints, secure logging, scaling, monitoring, and shutdown.
Best Practices
- Use managed identity with least-privilege Azure roles and keep credentials outside source code.
- Design handlers for replay, then checkpoint only after successful processing.
- Monitor consumer lag, processing failures, throttling, and batch utilization.
Avoid
- Do not log complete event bodies without an approved redaction policy.
- Do not assume checkpointing makes downstream side effects exactly-once.
- Do not reuse one consumer group for independent processing pipelines.
Frequently Asked Questions
Does this skill provision Azure resources?
No. It assumes the Event Hubs namespace, event hub, storage account, container, and permissions already exist.
Which authentication method does it use?
The examples use DefaultAzureCredential, which supports managed identity and local developer credentials.
Does checkpointing guarantee exactly-once processing?
No. Checkpoints record progress, but failures can cause replay. Use idempotent handlers or deduplication for side effects.
Can it send events to a specific partition?
Yes. It shows explicit partition identifiers and partition keys. Partition keys preserve ordering for related events.
Does it support receiving from a chosen position?
Yes. Examples cover earliest, latest, explicit offset, and timestamp-based starting positions.
Is the example logging suitable for production?
Not without review. Replace complete payload logging with approved metadata and redaction controls.