56 results available

integration-astro-ssr

posthog

·

Last changed

Hardened

This skill has been hardened by Chainguard

Last changed

This version passed the hardening gate. Hardening updated the skill content and independently checked the resulting changes. Classified findings before hardening: 3. Classified findings closed: 1. Classified findings remaining: 2. Unclassified scanner findings remaining: 0. Review findings closed: 0. Review findings remaining: 15.

Open before hardening

3

Medium

Open after hardening

2

Medium

File	Group	Subtype	Severity	Status
references/astro.md	Supply Chain & Install-Time Trust	—	Medium	Closed
references/astro.md	Prompt Injection	Indirect prompt injection	Medium	Open
references/EXAMPLE.md	Sensitive Data & Secret Exposure	Hardcoded secret	Medium	Open

3 findings

SKILL.md

PostHog integration for Astro (SSR)

This skill helps you add PostHog analytics to Astro (SSR) applications.

Workflow

Follow these steps in order to complete the integration:

basic-integration-1.0-begin.md - PostHog Setup - Begin ← Start here
basic-integration-1.1-edit.md - PostHog Setup - Edit
basic-integration-1.2-revise.md - PostHog Setup - Revise
basic-integration-1.3-conclude.md - PostHog Setup - Conclusion

Reference files

references/EXAMPLE.md - Astro (SSR) example project code
references/astro.md - Astro - docs
references/identify-users.md - Identify users - docs
references/basic-integration-1.0-begin.md - PostHog setup - begin
references/basic-integration-1.1-edit.md - PostHog setup - edit
references/basic-integration-1.2-revise.md - PostHog setup - revise
references/basic-integration-1.3-conclude.md - PostHog setup - conclusion

The example project shows the target implementation pattern. Consult the documentation for API details.

Key principles

Environment variables: Always use environment variables for PostHog keys. Never hardcode them.
Minimal changes: Add PostHog code alongside existing integrations. Don't replace or restructure existing code.
Match the example: Your implementation should follow the example project's patterns as closely as possible.

Framework guidelines

Always use the is:inline directive on PostHog script tags to prevent Astro from processing them and causing TypeScript errors
Use PUBLIC_ prefix for client-side environment variables in Astro (e.g., PUBLIC_POSTHOG_PROJECT_TOKEN)
Create a posthog.astro component in src/components/ for reusable initialization across pages
Import the PostHog component in a Layout and wrap all pages with that layout
Use posthog-node in API routes under src/pages/api/ for server-side event tracking
Store the posthog-node client instance in a singleton pattern (src/lib/posthog-server.ts) to avoid creating multiple clients
Pass the client session ID to server via X-PostHog-Session-Id header for unified session tracking

Identifying users

Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. If both frontend and backend code exist, pass the client-side session and distinct ID using X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers to maintain correlation.

Error tracking

Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries.

Install

Install with chainctl


chainctl skill install public/posthog/integration-astro-ssr:latest

Get started with chainctl

View source

Harden your own skills

Bring Chainguard's hardening pipeline to your first-party skills — custom rulesets, automated remediation, full audit trail.

Provenance

Upstream sourcehttps://github.com/posthog/skills

Upstream commitf322cbb89771c2cf5d3c2eafa973371633bef064

OCI reference

skills.cgr.dev/public/github.com/posthog/skills/posthog/all/skills/integration-astro-ssr:latest

License

MIT

Files

HARDENING.md

LICENSE

SKILL.md

references/EXAMPLE.md

references/astro.md

references/basic-integration-1.0-begin.md

references/basic-integration-1.1-edit.md

references/basic-integration-1.2-revise.md

references/basic-integration-1.3-conclude.md

references/identify-users.md

The trusted source for open source

Talk to an expert

Privacy

Terms

© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.