Skip to content
Back to search

walkerOS

Open-source tag manager for developers and agents

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/elbwalker/walkerOS with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/elbwalker/walkerOS'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/elbwalker--walkeros/badge.svg)](/listings/elbwalker--walkeros)

HTML

<a href="/listings/elbwalker--walkeros"><img src="/api/listings/elbwalker--walkeros/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 15 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "elbwalker",
  3. "owner": {
  4. "name": "elbwalker",
  5. "url": "https://github.com/elbwalker"
  6. },
  7. "description": "Claude Code plugins for walkerOS, the open-source event data collection platform.",
  8. "plugins": [
  9. {
  10. "name": "walkeros",
  11. "source": "./",
  12. "description": "Skills and MCP tools for walkerOS - build sources, destinations, transformers, and flows."
  13. }
  14. ]
  15. }
README.md · README · 218 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="left">
  2. <a href="https://www.walkeros.io">
  3. <img alt="walkerOS" title="walkerOS" src="https://www.walkeros.io/img/walkerOS_logo.svg" width="256px"/>
  4. </a>
  5. </p>
  6. # Event collection you own, version, and trust
  7. <div align="left">
  8. <a href="https://github.com/elbwalker/walkerOS/blob/main/LICENSE">
  9. <img src="https://img.shields.io/github/license/elbwalker/walkerOS" alt="License" />
  10. </a>
  11. <a href="https://www.walkeros.io/docs/">
  12. <img src="https://img.shields.io/badge/docs-www.walkeros.io/docs-yellow" alt="walkerOS Documentation" />
  13. </a>
  14. <a href="https://github.com/elbwalker/walkerOS/tree/main/apps/demos/react">
  15. <img src="https://img.shields.io/badge/React_demo-blue" alt="React demo" />
  16. </a>
  17. <a href="https://storybook.walkeros.io/">
  18. <img src="https://img.shields.io/badge/Storybook_demo-pink" alt="Storybook demo" />
  19. </a>
  20. <a href="https://www.npmjs.com/package/@walkeros/collector">
  21. <img src="https://img.shields.io/npm/v/@walkeros/collector" alt="npm version" />
  22. </a>
  23. </div>
  24. From browser to BigQuery and ad platforms - warehouse-native, and ready for AI
  25. agents via MCP.
  26. ## The problem
  27. GA4, custom tags, ad pixels - each one a separate setup, none of them agreeing
  28. on the same numbers. When something breaks, you can't see where.
  29. walkerOS is one collection layer for all of them.
  30. ## Why walkerOS?
  31. - **Config-as-code** - version control your tracking, review it in PRs, deploy
  32. with confidence
  33. - **Declarative tagging** - tag your UI in HTML, not scattered JavaScript
  34. - **Consent-native** - events queue until consent is given, then flush correctly
  35. to every destination
  36. - **Schema validation** - catch bad events at collection time, not weeks later
  37. in a dashboard
  38. - **One layer, many destinations** - send to your warehouse and ad platforms
  39. from a single event definition
  40. - **Warehouse-native** - events land clean and structured in your data
  41. warehouse, ready to query
  42. - **MIT licensed** - self-host anywhere, no vendor lock-in
  43. ## How it works
  44. ![walkerOS Architecture](https://raw.githubusercontent.com/elbwalker/walkerOS/main/website/static/diagrams/walkeros_readme.png)
  45. - **Sources:** Where events come from (browser, dataLayer, Express, AWS Lambda,
  46. GCP Functions, and more)
  47. - **Collector:** The processing engine (consent, validation, mapping, routing,
  48. enrichment)
  49. - **Destinations:** Where events go (GA4, Google Ads, Meta CAPI, BigQuery, and
  50. more)
  51. ## Two ways to install walkerOS
  52. Choose one based on your workflow and integration possibilities:
  53. | Mode | Description | Best For |
  54. | -------------- | ------------------------------------------------------------ | --------------------------------------- |
  55. | **Integrated** | Import directly into your TypeScript application | React/Next.js apps, TypeScript projects |
  56. | **Bundled** | Build a standalone script from JSON config with npx walkeros | Static sites, Docker deployments, CI/CD |
  57. **Integrated** (import into your app):
  58. ```typescript
  59. import { startFlow } from '@walkeros/collector';
  60. const { elb } = await startFlow({
  61. destinations: {
  62. console: {
  63. code: {
  64. type: 'console',
  65. config: {},
  66. push: (event) => console.log('Event:', event.name),
  67. },
  68. },
  69. },
  70. });
  71. await elb({ name: 'page view', data: { title: 'Home' } });
  72. // -> logs: Event: page view
  73. ```
  74. Wire a real source and destination once you are ready:
  75. ```typescript
  76. import { startFlow } from '@walkeros/collector';
  77. import { sourceBrowser } from '@walkeros/web-source-browser';
  78. import { destinationGtag } from '@walkeros/web-destination-gtag';
  79. await startFlow({
  80. sources: {
  81. browser: {
  82. code: sourceBrowser,
  83. config: { settings: { pageview: true } },
  84. },
  85. },
  86. destinations: {
  87. ga4: {
  88. code: destinationGtag,
  89. config: {
  90. settings: { ga4: { measurementId: 'G-XXX' } },
  91. },
  92. },
  93. },
  94. });
  95. ```
  96. **Bundled** (build from JSON config):
  97. ```json
  98. {
  99. "version": 4,
  100. "flows": {
  101. "default": {
  102. "config": {
  103. "platform": "web",
  104. "bundle": {
  105. "packages": {
  106. "@walkeros/collector": {},
  107. "@walkeros/web-source-browser": {},
  108. "@walkeros/web-destination-gtag": {}
  109. }
  110. }
  111. },
  112. "sources": {
  113. "browser": {
  114. "package": "@walkeros/web-source-browser",
  115. "config": { "settings": { "pageview": true } }
  116. }
  117. },
  118. "destinations": {
  119. "ga4": {
  120. "package": "@walkeros/web-destination-gtag",
  121. "config": {
  122. "settings": { "ga4": { "measurementId": "G-XXX" } }
  123. }
  124. }
  125. }
  126. }
  127. }
  128. }
  129. ```
  130. Then: `npx walkeros bundle flow.json`
  131. - **[Operating Modes](https://www.walkeros.io/docs/getting-started/modes/)**
  132. - **[Quickstart guide for React](https://www.walkeros.io/docs/getting-started/quickstart/react)**
  133. - **[Full Documentation](https://www.walkeros.io/docs/)** - Complete guides and
  134. API reference
  135. - **[Destinations](https://www.walkeros.io/docs/destinations/)** - GA4, Meta,
  136. BigQuery, and more
  137. - **[React Demo](https://github.com/elbwalker/walkerOS/tree/main/apps/demos/react)**
  138. - **[Storybook](https://storybook.walkeros.io/)**
  139. ## AI-ready via MCP
  140. walkerOS exposes a Model Context Protocol (MCP) interface. AI agents can read
  141. your event schema, suggest tracking definitions, and generate integration code -
  142. making your event layer programmable, not just configurable.
  143. In Claude Code, one plugin installs both MCP servers and the walkerOS skills:
  144. ```
  145. /plugin marketplace add elbwalker/walkerOS
  146. /plugin install walkeros@elbwalker
  147. ```
  148. For any other MCP client, add the servers to its configuration:
  149. ```json
  150. {
  151. "mcpServers": {
  152. "walkeros-flow": {
  153. "command": "npx",
  154. "args": ["@walkeros/mcp"]
  155. },
  156. "walkeros-source-browser": {
  157. "command": "npx",
  158. "args": ["@walkeros/mcp-source-browser"]
  159. }
  160. }
  161. }
  162. ```
  163. Loading a flow, validating it, and simulating an event all run locally, no
  164. account needed. See the [MCP docs](https://www.walkeros.io/docs/apps/mcp).
  165. Coming from Google Tag Manager? See
  166. [walkerOS vs. GTM](https://www.walkeros.io/docs/comparisons/gtm).
  167. ## Contributing
  168. ⭐️ Help us grow and star us. See our
  169. [Contributing Guidelines](https://www.walkeros.io/docs/contributing) to get
  170. involved.
  171. ## Support
  172. Need help? Start a
  173. [discussion](https://github.com/elbwalker/walkerOS/discussions), or reach out
  174. via [email](mailto:hello@elbwalker.com).
  175. For more insights, visit the
  176. [talks repository](https://github.com/elbwalker/talks).
  177. ## License
  178. Licensed under the [MIT License](./LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.