Import wizard
Step-by-step wizard: file selection, column mapping, preview, and generation.
Import frameworks. Link evidence. Query everything. Evolve with every update. Open source.
Philosophically, Crosswalker is an ontology lifecycle management engine. In practice, it turns your Obsidian vault into an operational compliance knowledge graph. Import structured frameworks, crosswalk between standards, link evidence to controls with structured metadata, and query everything — all in plain markdown you own. AI-ready from day one.
Import wizard
Step-by-step wizard: file selection, column mapping, preview, and generation.
Framework crosswalks
Map relationships between frameworks. Link NIST to CIS to MITRE with typed edges and metadata.
Evidence mapping
Link policies, audit findings, and technical docs directly to framework controls with edge metadata.
AI-ready
Plain markdown is the best format for RAG pipelines, embeddings, and AI agents. Your knowledge base is instantly indexable — no export required.
Community configs
Save, share, and reuse import configurations. Fingerprint-based matching for similar files. Import what others have already mapped.
Progressive depth
Start with the guided UI wizard. Graduate to config-as-code for repeatable imports. Add CLI tooling for automation and CI/CD.
Tool-agnostic
Works with Obsidian Bases or plain markdown search. Your data is just files — no lock-in.
Free and open source
MIT licensed. Own your tooling. Contribute features, framework configs, or documentation.
Built for GRC
Compliance, risk, and audit teams spend weeks mapping frameworks and linking evidence manually. Crosswalker automates the structure so you can focus on the analysis.
Frameworks change. You're ready.
When NIST updates or CIS restructures, Crosswalker detects what changed and helps you update without losing your evidence mappings.
Crosswalker is early and moving fast. Here’s how to participate:
Star on GitHub
Star the repo to follow development and show support.
Contribute
Read the contributing guide — code, docs, framework configs, or bug reports all welcome.
Follow the roadmap
See what’s being built and the architectural decisions behind it.
Read the blog
Follow development updates and changelog.