{"documents":{"roadmap":"# Roadmap\n\n> FoxIO Labs – JA4+ Network Fingerprinting Educational Platform\n\nThis document outlines the development roadmap for the FoxIO Labs educational platform,\nan open-source resource for learning about JA4+ network fingerprinting methods created by\nJohn Althouse at FoxIO.\n\n---\n\n## ✅ Completed (v1.0)\n\n- Core JA4+ educational content covering the full fingerprinting suite\n  - JA4 (TLS Client Fingerprinting)\n  - JA4S (TLS Server Response)\n  - JA4H (HTTP Client Fingerprinting)\n  - JA4L (Light Distance / Locality)\n  - JA4X (X.509 Certificate Fingerprinting)\n  - JA4SSH (SSH Traffic Fingerprinting)\n  - JA4T (TCP Client Fingerprinting)\n  - JA4TS (TCP Server Response)\n  - JA4TScan (Active TCP Fingerprint Scanner)\n- Quick Labs for all fingerprint types\n- Wireshark plugin tutorial\n- Inbound Detection guide\n- Dark/light theme support with system preference detection\n- Responsive mobile design\n- SEO optimization (sitemap, robots.txt, meta tags, Open Graph)\n\n## 🔄 In Progress (v1.1)\n\n- FAQ page with comprehensive Q&A\n- API endpoints for content and fingerprint data\n- MCP client registration with PlatPhorm News Network\n- JSON-LD structured data for improved search engine visibility\n- Breadcrumb navigation\n- Social sharing integration\n- Open source documentation (CONTRIBUTING, CODE_OF_CONDUCT, SECURITY)\n- i18n foundation for multilingual support\n\n## 📅 Planned (v1.2)\n\n- Interactive JA4+ fingerprint calculator\n- Live packet capture analysis tool\n- Community contribution portal\n- Multi-language support (Spanish, French, German, Japanese, Korean)\n- Advanced search functionality\n- User-submitted fingerprint database entries\n- JA4+ certification program\n- Integration with SIEM/SOAR platforms\n\n## 🚀 Future (v2.0)\n\n- Real-time JA4+ fingerprint analysis dashboard\n- API rate limiting and authentication\n- Community forums\n- JA4+ plugin marketplace\n- Automated threat intelligence feeds\n- Machine learning-based fingerprint clustering\n\n---\n\n## About JA4+\n\nJA4+ is an open-source suite of network fingerprinting methods created by\n[John Althouse](https://github.com/jalthouse) at [FoxIO](https://foxio.io).\nIt is adopted by major platforms including Wireshark, Arkime, Zeek, Suricata,\nAWS Security Lake, Google SecOps, F5, Barracuda, GreyNoise, Hunt.io, Censys,\nDriftnet, NGINX, HAProxy, and many more.\n\n## About This Project\n\nThis educational platform is part of the\n[PlatPhorm News Network](https://platphormnews.com) (*.platphormnews.com),\ncreated by Michael Barbine, PH3AR, and the PlatPhorm News Network.\n\n---\n\n*Last updated: 2025*\n","contributing":"# Contributing to FoxIO Labs\n\nThank you for your interest in contributing to the FoxIO Labs JA4+ educational\nplatform! This project is part of the [PlatPhorm News Network](https://platphormnews.com)\nand serves as an open-source resource for learning about JA4+ network\nfingerprinting methods.\n\n## Table of Contents\n\n- [How to Contribute](#how-to-contribute)\n- [Development Setup](#development-setup)\n- [Code Style](#code-style)\n- [Pull Request Process](#pull-request-process)\n- [Issue Reporting](#issue-reporting)\n- [Content Contributions](#content-contributions)\n- [Code of Conduct](#code-of-conduct)\n- [License](#license)\n\n## How to Contribute\n\nThere are many ways to contribute:\n\n- **Report bugs** – Found something broken? Open an issue.\n- **Suggest features** – Have an idea? We'd love to hear it.\n- **Fix issues** – Browse open issues and submit a pull request.\n- **Improve documentation** – Help make the docs clearer and more complete.\n- **Add educational content** – Contribute tutorials, guides, or lab exercises\n  about JA4+ fingerprinting.\n\n## Development Setup\n\n### Prerequisites\n\n- [Node.js](https://nodejs.org/) 18.0 or later\n- [pnpm](https://pnpm.io/) (recommended package manager)\n- Git\n\n### Getting Started\n\n1. **Fork the repository** on GitHub.\n\n2. **Clone your fork:**\n\n   ```bash\n   git clone https://github.com/<your-username>/threatrelay-webby.git\n   cd threatrelay-webby/\n   ```\n\n3. **Install dependencies:**\n\n   ```bash\n   pnpm install\n   ```\n\n4. **Start the development server:**\n\n   ```bash\n   pnpm dev\n   ```\n\n5. **Open the site** at [http://localhost:3000](http://localhost:3000).\n\n### Tech Stack\n\n- **Framework:** [Next.js 15](https://nextjs.org/) with the App Router\n- **Language:** [TypeScript](https://www.typescriptlang.org/)\n- **Styling:** [Tailwind CSS](https://tailwindcss.com/)\n- **UI Components:** [Radix UI](https://www.radix-ui.com/) primitives\n- **Icons:** [Lucide React](https://lucide.dev/)\n- **Themes:** [next-themes](https://github.com/pacocoursey/next-themes)\n\n## Code Style\n\n- Write all new code in **TypeScript**.\n- Use **Tailwind CSS** utility classes for styling; avoid custom CSS unless\n  absolutely necessary.\n- Follow the existing component patterns in the `components/` directory.\n- Use `lucide-react` for icons.\n- Keep components small and focused on a single responsibility.\n- Use meaningful variable and function names.\n- Prefer named exports for components (e.g., `export function SiteHeader()`).\n\n### File Naming\n\n- React components: `kebab-case.tsx` (e.g., `site-header.tsx`)\n- Pages: `page.tsx` inside route directories under `app/`\n- Utilities: `kebab-case.ts` inside `lib/`\n\n## Pull Request Process\n\n1. **Create a branch** from `main` with a descriptive name:\n\n   ```bash\n   git checkout -b feature/interactive-calculator\n   ```\n\n2. **Make your changes** and commit with clear, descriptive messages.\n\n3. **Test your changes** locally:\n\n   ```bash\n   pnpm build\n   ```\n\n4. **Push your branch** and open a pull request against `main`.\n\n5. **Describe your changes** in the PR description, including:\n   - What the change does\n   - Why it's needed\n   - Screenshots (for UI changes)\n   - Any breaking changes\n\n6. **Wait for review.** A maintainer will review your PR and may request\n   changes before merging.\n\n### PR Checklist\n\n- [ ] Code compiles without errors (`pnpm build`)\n- [ ] Changes are tested locally\n- [ ] New pages include proper metadata (`title`, `description`)\n- [ ] UI is responsive and works in both light and dark themes\n- [ ] No sensitive data or credentials are included\n\n## Issue Reporting\n\nWhen reporting a bug, please include:\n\n- A clear and descriptive title\n- Steps to reproduce the issue\n- Expected behavior vs. actual behavior\n- Browser and OS information\n- Screenshots or error messages, if applicable\n\nFor feature requests, describe:\n\n- The problem you're trying to solve\n- Your proposed solution\n- Any alternatives you've considered\n\n## Content Contributions\n\nJA4+ educational content must be **technically accurate**. When contributing\ncontent about JA4+ fingerprinting methods:\n\n- **Verify all technical claims** against the official JA4+ documentation and\n  source code at [FoxIO's JA4+ repository](https://github.com/FoxIO-LLC/ja4).\n- **Cite sources** when referencing specific fingerprint behaviors or values.\n- **Use correct terminology** as defined by the JA4+ specification.\n- **Test fingerprint examples** when possible to ensure accuracy.\n- **Do not speculate** about fingerprint values; only document verified\n  behaviors.\n\nContent contributions are reviewed for both technical accuracy and clarity\nbefore being merged.\n\n## Code of Conduct\n\nThis project follows the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md).\nBy participating, you are expected to uphold this code. Please report\nunacceptable behavior to the project maintainers.\n\n## License\n\nBy contributing to this project, you agree that your contributions will be\nlicensed under the project's existing license. Educational content about JA4+\nis provided under the [FoxIO License](https://github.com/FoxIO-LLC/ja4/blob/main/LICENSE).\nPlease review the [LICENSE](LICENSE) file for details.\n\n---\n\nThank you for helping make JA4+ network fingerprinting education accessible to\neveryone! 🎉\n","code_of_conduct":"# Contributor Covenant Code of Conduct\n\n## Our Pledge\n\nWe as members, contributors, and leaders pledge to make participation in our\ncommunity a harassment-free experience for everyone, regardless of age, body\nsize, visible or invisible disability, ethnicity, sex characteristics, gender\nidentity and expression, level of experience, education, socio-economic status,\nnationality, personal appearance, race, caste, color, religion, or sexual\nidentity and orientation.\n\nWe pledge to act and interact in ways that contribute to an open, welcoming,\ndiverse, inclusive, and healthy community.\n\n## Our Standards\n\nExamples of behavior that contributes to a positive environment for our\ncommunity include:\n\n- Demonstrating empathy and kindness toward other people\n- Being respectful of differing opinions, viewpoints, and experiences\n- Giving and gracefully accepting constructive feedback\n- Accepting responsibility and apologizing to those affected by our mistakes,\n  and learning from the experience\n- Focusing on what is best not just for us as individuals, but for the overall\n  community\n\nExamples of unacceptable behavior include:\n\n- The use of sexualized language or imagery, and sexual attention or advances of\n  any kind\n- Trolling, insulting or derogatory comments, and personal or political attacks\n- Public or private harassment\n- Publishing others' private information, such as a physical or email address,\n  without their explicit permission\n- Other conduct which could reasonably be considered inappropriate in a\n  professional setting\n\n## Enforcement Responsibilities\n\nCommunity leaders are responsible for clarifying and enforcing our standards of\nacceptable behavior and will take appropriate and fair corrective action in\nresponse to any behavior that they deem inappropriate, threatening, offensive,\nor harmful.\n\nCommunity leaders have the right and responsibility to remove, edit, or reject\ncomments, commits, code, wiki edits, issues, and other contributions that are\nnot aligned to this Code of Conduct, and will communicate reasons for moderation\ndecisions when appropriate.\n\n## Scope\n\nThis Code of Conduct applies within all community spaces, and also applies when\nan individual is officially representing the community in public spaces.\nExamples of representing our community include using an official email address,\nposting via an official social media account, or acting as an appointed\nrepresentative at an online or offline event.\n\n## Enforcement\n\nInstances of abusive, harassing, or otherwise unacceptable behavior may be\nreported to the community leaders responsible for enforcement via the project's\nGitHub issue tracker or by contacting the maintainers directly.\n\nAll complaints will be reviewed and investigated promptly and fairly.\n\nAll community leaders are obligated to respect the privacy and security of the\nreporter of any incident.\n\n## Enforcement Guidelines\n\nCommunity leaders will follow these Community Impact Guidelines in determining\nthe consequences for any action they deem in violation of this Code of Conduct:\n\n### 1. Correction\n\n**Community Impact:** Use of inappropriate language or other behavior deemed\nunprofessional or unwelcome in the community.\n\n**Consequence:** A private, written warning from community leaders, providing\nclarity around the nature of the violation and an explanation of why the\nbehavior was inappropriate. A public apology may be requested.\n\n### 2. Warning\n\n**Community Impact:** A violation through a single incident or series of\nactions.\n\n**Consequence:** A warning with consequences for continued behavior. No\ninteraction with the people involved, including unsolicited interaction with\nthose enforcing the Code of Conduct, for a specified period of time. This\nincludes avoiding interactions in community spaces as well as external channels\nlike social media. Violating these terms may lead to a temporary or permanent\nban.\n\n### 3. Temporary Ban\n\n**Community Impact:** A serious violation of community standards, including\nsustained inappropriate behavior.\n\n**Consequence:** A temporary ban from any sort of interaction or public\ncommunication with the community for a specified period of time. No public or\nprivate interaction with the people involved, including unsolicited interaction\nwith those enforcing the Code of Conduct, is allowed during this period.\nViolating these terms may lead to a permanent ban.\n\n### 4. Permanent Ban\n\n**Community Impact:** Demonstrating a pattern of violation of community\nstandards, including sustained inappropriate behavior, harassment of an\nindividual, or aggression toward or disparagement of classes of individuals.\n\n**Consequence:** A permanent ban from any sort of public interaction within the\ncommunity.\n\n## Attribution\n\nThis Code of Conduct is adapted from the [Contributor Covenant][homepage],\nversion 2.1, available at\n[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].\n\nCommunity Impact Guidelines were inspired by\n[Mozilla's code of conduct enforcement ladder][Mozilla CoC].\n\nFor answers to common questions about this code of conduct, see the FAQ at\n[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at\n[https://www.contributor-covenant.org/translations][translations].\n\n[homepage]: https://www.contributor-covenant.org\n[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html\n[Mozilla CoC]: https://github.com/mozilla/diversity\n[FAQ]: https://www.contributor-covenant.org/faq\n[translations]: https://www.contributor-covenant.org/translations\n","security":"# Security Policy\n\n## Supported Versions\n\n| Version | Supported          |\n| ------- | ------------------ |\n| 1.1.x   | ✅ Active support  |\n| 1.0.x   | ✅ Security fixes  |\n| < 1.0   | ❌ Not supported   |\n\n## Reporting a Vulnerability\n\nWe take the security of the FoxIO Labs educational platform seriously. If you\ndiscover a security vulnerability, please report it responsibly.\n\n### How to Report\n\n1. **Do not** open a public GitHub issue for security vulnerabilities.\n2. Report vulnerabilities via GitHub's private\n   [Security Advisory](https://github.com/mbarbine/threatrelay-webby/security/advisories/new)\n   feature.\n3. Alternatively, contact the maintainers directly through the repository's\n   security contacts.\n\n### What to Include\n\n- A clear description of the vulnerability\n- Steps to reproduce the issue\n- The potential impact of the vulnerability\n- Any suggested fixes (optional but appreciated)\n\n## Response Timeline\n\n- **Acknowledgment:** Within 48 hours of receiving the report\n- **Initial assessment:** Within 5 business days\n- **Fix and disclosure:** Coordinated with the reporter, typically within 30 days\n\n## Responsible Disclosure Policy\n\nWe follow responsible disclosure practices:\n\n- We will work with you to understand and address the issue.\n- We will credit you in the security advisory (unless you prefer to remain\n  anonymous).\n- We ask that you give us reasonable time to address the issue before any public\n  disclosure.\n- We will not take legal action against researchers who follow this policy.\n\n## Scope\n\nThe following are in scope for security reports:\n\n### In Scope\n\n- **Web application** – The Next.js application and its pages\n- **API endpoints** – Any API routes under `/api/`\n- **Dependencies** – Vulnerabilities in third-party packages\n- **Configuration** – Misconfigurations that could lead to security issues\n- **Authentication/Authorization** – Any access control issues\n\n### Out of Scope\n\n- Issues in third-party services we link to (FoxIO, GitHub, etc.)\n- Social engineering attacks\n- Denial of service attacks\n- Issues that require physical access to a user's device\n- Issues in browsers or operating systems\n\n## Security Best Practices\n\nWhen contributing to this project, please follow these security guidelines:\n\n- Never commit secrets, API keys, or credentials to the repository.\n- Keep dependencies up to date and audit them regularly.\n- Follow the principle of least privilege for any access controls.\n- Sanitize and validate all user input.\n- Use HTTPS for all external requests.\n\n---\n\nThank you for helping keep the FoxIO Labs platform and its users safe! 🔒\n"},"available":["roadmap","contributing","code_of_conduct","security"],"missing":[]}