56 results available
Sign in
Skills directory

logs-nodejs

posthog

·

Last changed
Hardened

This skill has been hardened by Chainguard

Last changed

This version passed the hardening gate. Hardening applied 4 targeted changes and preserved all other text. Classified findings before hardening: 4. Classified findings closed: 0. Classified findings remaining: 4. Unclassified scanner findings remaining: 0. Review findings closed: 0. Review findings remaining: 12.

Open before hardening

4

Medium
Open after hardening

4

Medium
Expand
File
Group
Subtype
Severity
Status
SKILL.md

Sensitive Data & Secret Exposure

Hardcoded secret

Medium
Open
references/best-practices.md

Sensitive Data & Secret Exposure

Hardcoded secret

Medium
Open
references/nodejs.md

Sensitive Data & Secret Exposure

Hardcoded secret

Medium
Open
references/start-here.md

Sensitive Data & Secret Exposure

Hardcoded secret

Medium
Open

4 findings

SKILL.md

PostHog logs for Node.js

This skill helps you add PostHog log ingestion to Node.js applications.

Reference files

  • references/nodejs.md - Node.js logs installation - docs
  • references/start-here.md - Getting started with logs - docs
  • references/search.md - Search logs - docs
  • references/best-practices.md - Logging best practices - docs
  • references/troubleshooting.md - Logs troubleshooting - docs
  • references/link-session-replay.md - Link session replay - docs
  • references/debug-logs-mcp.md - Debug logs with mcp - docs

Consult the documentation for API details and framework-specific patterns.

Key principles

  • Environment variables: Always use environment variables for PostHog keys and OpenTelemetry endpoints. Never hardcode them.
  • Minimal changes: Add log export alongside existing logging. Don't replace or restructure existing logging code.
  • OpenTelemetry: PostHog logs use the OpenTelemetry protocol. Configure an OTLP exporter pointed at PostHog's ingest endpoint.
  • Structured logging: Prefer structured log formats with key-value properties over plain text messages.

Framework guidelines

No specific framework guidelines.

Install

Install with chainctl
chainctl skill install public/posthog/logs-nodejs: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/logs/skills/nodejs:latest

License

MIT

Files

HARDENING.md

LICENSE

SKILL.md

references/best-practices.md

references/debug-logs-mcp.md

references/link-session-replay.md

references/nodejs.md

references/search.md

references/start-here.md

references/troubleshooting.md

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing

Solutions

FedRAMPPCI DSSCMMC 2.0SOC 2Golden ImagesCVE RemediationPublic SectorStartups

Customers

Customer StoriesChainguard Reviews

Resources

Events & WebinarsSupply Chain Security 101Chainguard CoursesDocumentationTrust CenterChainguard Slack Community

Company

About UsBlogOpen Source LeadershipPartnersNewsroomCareersLegal
© 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.