You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<pstyle="margin: 0010px0; font-size: 24px; font-weight: 700; color: #333;">FREE FOR OPEN SOURCE PROJECTS. FOREVER.</p>
17
-
<pstyle="margin: 0; font-size: 16px; line-height: 1.5; color: #333;">Open source built the tech stack you use daily. We make it faster to maintain. If your project is open source, our tools are free forever—and we reinvest 10% of revenue into the OSS projects in our own stack.</p>
<pclass="support-hero-title">FREE FOR OPEN SOURCE PROJECTS. FOREVER.</p>
16
+
<pclass="support-hero-text">Open source built the tech stack you use daily. We make it faster to maintain. If your project is open source, our tools are free forever—and we reinvest 10% of revenue into the OSS projects in our own stack.</p>
<pstyle="margin: 0010px0;">You're already donating your time. We eliminate the context-switching overhead that kills your flow state—so you can spend more time shipping code, less time chasing PR status.</p>
25
23
<pstyle="margin: 0;">We proudly donate to and support: <ahref="https://projectbluefin.io/">Bluefin Linux</a>, <ahref="https://freebsd.org/">FreeBSD</a>, <ahref="https://ghostbsd.org/">GhostBSD</a>, <ahref="https://github.com/golangci/golangci-lint">golangci-lint</a>, <ahref="https://www.netbsd.org/">NetBSD</a>, and <ahref="https://osuosl.org/">OSU Open Source Lab</a>.</p>
<p><strongstyle="color: var(--yellow);">Ready to Review</strong> — Picks the best reviewer based on who's actually active and recently touched the code. Eliminates "who's blocking this PR?" context hunts with turn-based tracking that shows exactly who needs to act. <ahref="https://github.com/codeGROOVE-dev/ready-to-review">View on GitHub →</a></p>
29
+
<p><strongstyle="color: var(--yellow);"><ahref="https://github.com/codeGROOVE-dev/ready-to-review"style="color: var(--yellow);">Ready to Review</a></strong> — Web dashboard for tracking PR status and turn-based review workflows.</p>
32
30
33
-
<p><strongstyle="color: var(--yellow);">Goose</strong> — Auto-detects when PRs are stalled on you. Cuts PR cycle time without micromanagement. <ahref="https://github.com/codeGROOVE-dev/goose">View on GitHub →</a></p>
31
+
<p><strongstyle="color: var(--yellow);"><ahref="https://github.com/codeGROOVE-dev/best-reviewer"style="color: var(--yellow);">best-reviewer</a></strong> — The intelligent bot that assigns reviewers to your PRs.</p>
32
+
33
+
<p><strongstyle="color: var(--yellow);"><ahref="https://github.com/codeGROOVE-dev/goose"style="color: var(--yellow);">Goose</a></strong> — Auto-detects when PRs are stalled on you. Cuts PR cycle time without micromanagement.</p>
<p><strongstyle="color: var(--yellow);"><ahref="https://github.com/codeGROOVE-dev/slacker"style="color: var(--yellow);">Slacker</a></strong> — Hyperintelligent Slack bot for GitHub notifications.</p>
34
38
35
39
<pstyle="margin-bottom: 0;">Explore all our open source work at <ahref="https://github.com/orgs/codeGROOVE-dev/repositories">github.com/codeGROOVE-dev</a></p>
<pstyle="margin: 0; font-size: 16px; line-height: 1.5; color: #333;">Our team previously ran security programs at companies like Google and Chainguard. We get it.</p>
<li><strong>Zero Trust</strong>: Hardware-backed cryptographic identity and encryption are our security perimeter</li>
26
-
<li><strong>Defense in depth</strong>: Every layer fails—we rely on overlapping controls (<ahref="https://en.wikipedia.org/wiki/Swiss_cheese_model">swiss cheese model</a>)</li>
27
-
<li><strong>Ephemeral secrets</strong>: All secrets leak eventually. We prefer <ahref="https://openid.net/developers/how-connect-works/">OIDC</a>. When unavoidable, we rely on a runtime KMS — never transferring secrets via disk, <ahref="https://www.gnu.org/software/c-intro-and-ref/manual/html_node/Command_002dline-Parameters.html">argv</a>, or <ahref="https://man7.org/linux/man-pages/man7/environ.7.html">environ(7)</a>.</li>
28
-
<li><strong>Minimal data surface</strong>: Less data = less risk. Metadata cache only (21-day TTL), 0 persistent user data</li>
29
-
<li><strong>Minimal supply chain</strong>: Most services have 0-1 external deps. We use <ahref="https://github.com/ko-build/ko">ko</a>+<ahref="https://images.chainguard.dev/">Chainguard Images</a></li>
30
-
<li><strong>No data monetization</strong>: We never sell your data. Third-party sharing limited to operational requirements/li>
31
-
<li><strong>Radical transparency</strong>: Audit our code anytime—if it's not open-source yet, just ask!</li>
32
-
</ul>
20
+
<divclass="support-section">
21
+
<h2>OUR SECURITY PRINCIPLES</h2>
22
+
<ul>
23
+
<li><strong>Zero Trust</strong>: Hardware-backed cryptographic identity and encryption are our security perimeter</li>
24
+
<li><strong>Defense in depth</strong>: Every layer fails—we rely on overlapping controls (<ahref="https://en.wikipedia.org/wiki/Swiss_cheese_model">swiss cheese model</a>)</li>
25
+
<li><strong>Ephemeral secrets</strong>: All secrets leak eventually. We prefer <ahref="https://openid.net/developers/how-connect-works/">OIDC</a>. When unavoidable, we rely on a runtime KMS — never transferring secrets via disk, <ahref="https://www.gnu.org/software/c-intro-and-ref/manual/html_node/Command_002dline-Parameters.html">argv</a>, or <ahref="https://man7.org/linux/man-pages/man7/environ.7.html">environ(7)</a>.</li>
26
+
<li><strong>Minimal data surface</strong>: Less data = less risk. Metadata cache only (21-day TTL), 0 persistent user data</li>
27
+
<li><strong>Minimal supply chain</strong>: Most services have 0-1 external deps. We use <ahref="https://github.com/ko-build/ko">ko</a>+<ahref="https://images.chainguard.dev/">Chainguard Images</a></li>
28
+
<li><strong>No data monetization</strong>: We never sell your data. Third-party sharing limited to operational requirements</li>
29
+
<li><strong>Radical transparency</strong>: Audit our code anytime—if it's not open-source yet, just ask!</li>
<p>Our team has guided companies through SOC 2 certification. Rather than retrofit compliance later, we're engineering our security controls to meet SOC 2 standards from day one.</p>
<p>Find a vulnerability? Check out our <ahref="/.well-known/security.txt">security.txt</a>.</p>
48
-
<pstyle="margin-bottom: 0;">We could literally talk all day long about security. If you are interested, <ahref="https://calendar.app.google/TbQmeX8iWnvx6Ci89">set up a call!</a></p>
43
+
<divclass="support-section">
44
+
<h2>VULNERABILITY DISCLOSURE</h2>
45
+
<p>Found a security issue? Check out our <ahref="/.well-known/security.txt">security.txt</a> for reporting instructions.</p>
46
+
</div>
47
+
48
+
<divclass="about-contact-section">
49
+
<h2>WANT TO DISCUSS SECURITY?</h2>
50
+
<p>We could talk all day about security architecture, compliance, or threat modeling.</p>
51
+
<divclass="about-contact-links">
52
+
<ahref="https://calendar.app.google/TbQmeX8iWnvx6Ci89"class="cta-button cta-button--green">Schedule a Call</a>
<pstyle="margin: 0010px0; font-size: 24px; font-weight: 700; color: #333;">WE'RE HERE TO HELP</p>
17
-
<pstyle="margin: 0; font-size: 16px; line-height: 1.5; color: #333;">Whether you have questions, need technical assistance, or want to provide feedback, we've got you covered.</p>
0 commit comments