azure-postgres-ts
Build Secure Azure PostgreSQL Clients in TypeScript
Connecting Node.js applications to Azure PostgreSQL requires secure authentication, pooling, and reliable query patterns. This skill provides focused TypeScript guidance for password and Microsoft Entra ID connections.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "azure-postgres-ts" from https://skillstore.io/skills/sickn33-azure-postgres-ts.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-postgres-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-postgres-ts". Create a production connection approach using Microsoft Entra ID for an API service.
Expected outcome:
- Use DefaultAzureCredential with the Azure PostgreSQL token scope.
- Create an SSL-enabled pool with bounded size and connection timeouts.
- Refresh tokens before expiration and close replaced pools.
Using "azure-postgres-ts". Plan safe creation of a user and related order in one operation.
Expected outcome:
A transaction plan begins the operation, inserts both records with parameters, commits on success, rolls back on failure, and releases the client.
Using "azure-postgres-ts". Explain how to diagnose common PostgreSQL failures.
Expected outcome:
- Map known database error codes to useful application outcomes.
- Avoid exposing credentials, tokens, query parameters, or sensitive error details.
- Re-throw unexpected failures after recording sanitized operational context.
Security Audit
SafeAll 121 static findings are false positives caused by Markdown formatting, documentation URLs, standard process.env configuration, and illustrative parameterized SQL. The file contains guidance only, with no executable scripts, hidden-file access, credential exfiltration, system reconnaissance, or prompt injection.
Risk Factors
⚙️ External commands (42)
🌐 Network access (8)
📁 Filesystem access (3)
🔑 Env variables (42)
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-postgres-ts/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-postgres-ts?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-postgres-ts?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-postgres-ts/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-postgres-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-postgres-ts security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-postgres-ts/audits/5BibTeX citation
@techreport{sickn33-sickn33-azure-postgres-ts-2026,
author = {sickn33},
title = {azure-postgres-ts security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-azure-postgres-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-postgres-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-postgres-ts/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-azure-postgres-ts:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Create a service connection
Build a first TypeScript connection with password authentication, SSL verification, and reliable cleanup.
Adopt passwordless authentication
Replace stored database passwords with Microsoft Entra ID tokens and managed identity configuration.
Harden production data access
Review pooling, transactions, parameterized queries, token refresh, and database error handling.
Try These Prompts
Create a TypeScript Azure PostgreSQL client using node-postgres, password authentication, SSL verification, environment variables, and guaranteed cleanup.
Build a reusable node-postgres pool with sensible limits, timeouts, parameterized queries, error handling, and graceful shutdown.
Convert my Azure PostgreSQL configuration to DefaultAzureCredential, explain required environment values, and implement token refresh without logging secrets.
Design a typed TypeScript data layer using pooling, transaction helpers, parameterized queries, Entra ID token renewal, metrics, and structured database errors.
Best Practices
- Prefer Microsoft Entra ID and managed identities when the deployment environment supports them.
- Use parameterized queries, verified SSL, bounded pools, explicit timeouts, and graceful shutdown.
- Test token renewal, transaction rollback, connection exhaustion, and database outages before production release.
Avoid
- Do not concatenate user input into SQL statements.
- Do not embed database passwords, access tokens, or complete connection strings in source code or logs.
- Do not create an unbounded pool or leave clients checked out after failures.