Skip to content

Add Stytch sponsor logos and update README #509

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

howard-stytch
Copy link

@howard-stytch howard-stytch commented Jul 15, 2025

Added Stytch sponsor information and logos to the readme file.

Summary by CodeRabbit

  • Documentation
    • Added a "Sponsors" section to the top of the README, highlighting Stytch with a logo, description, and link.

Copy link

coderabbitai bot commented Jul 22, 2025

Walkthrough

A "Sponsors" section was added near the top of the README.md file, highlighting Stytch as a sponsor with their logo, a tagline, and a brief description. The section is visually separated by horizontal rules. No other content or files were changed.

Changes

File(s) Change Summary
README.md Added a "Sponsors" section featuring Stytch's logo, tagline, and description.

Estimated code review effort

1 (~2 minutes)

Poem

A sponsor hops into our README bright,
Stytch’s logo gleams in adaptive light.
With thanks and a link, we give them a cheer,
For helping our project leap forward this year.
🐇✨


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
README.md (1)

12-40: Consider pure-Markdown fallback to silence MD033 or disable the rule

Inline HTML is perfectly valid in GitHub-flavoured Markdown and often required for precise layout, but markdownlint (MD033) will keep complaining.
Options:

  1. Convert to standard Markdown image syntax and centering via <p align="center"> only if the extra <picture> sources are not strictly needed.
  2. Keep the HTML but add a repo-level .markdownlint.json suppressing MD033 for README.md.

Either path avoids recurring linter noise.
Up to you which is less intrusive.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9b91edf and 6260830.

⛔ Files ignored due to path filters (2)
  • sponsor/stytch-dark.svg is excluded by !**/*.svg
  • sponsor/stytch-light.svg is excluded by !**/*.svg
📒 Files selected for processing (1)
  • README.md (1 hunks)
🪛 markdownlint-cli2 (0.17.2)
README.md

12-12: Inline HTML
Element: div

(MD033, no-inline-html)


13-13: Inline HTML
Element: a

(MD033, no-inline-html)


14-14: Inline HTML
Element: picture

(MD033, no-inline-html)


15-15: Inline HTML
Element: source

(MD033, no-inline-html)


16-16: Inline HTML
Element: source

(MD033, no-inline-html)


17-17: Inline HTML
Element: img

(MD033, no-inline-html)


17-17: Images should have alternate text (alt text)

(MD045, no-alt-text)


20-20: Inline HTML
Element: p

(MD033, no-inline-html)


21-21: Inline HTML
Element: a

(MD033, no-inline-html)


22-22: Inline HTML
Element: b

(MD033, no-inline-html)


22-22: Inline HTML
Element: br

(MD033, no-inline-html)

🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md

12-12: Inline HTML
Element: div

(MD033, no-inline-html)


13-13: Inline HTML
Element: a

(MD033, no-inline-html)


14-14: Inline HTML
Element: picture

(MD033, no-inline-html)


15-15: Inline HTML
Element: source

(MD033, no-inline-html)


16-16: Inline HTML
Element: source

(MD033, no-inline-html)


17-17: Inline HTML
Element: img

(MD033, no-inline-html)


17-17: Images should have alternate text (alt text)

(MD045, no-alt-text)


20-20: Inline HTML
Element: p

(MD033, no-inline-html)


21-21: Inline HTML
Element: a

(MD033, no-inline-html)


22-22: Inline HTML
Element: b

(MD033, no-inline-html)


22-22: Inline HTML
Element: br

(MD033, no-inline-html)

Comment on lines +15 to +23
<source width="200px" media="(prefers-color-scheme: dark)" srcset="./sponsor/stytch-light.svg">
<source width="200px" media="(prefers-color-scheme: light)" srcset="./sponsor/stytch-dark.svg">
<img width="200px" src="./sponsor/stytch-dark.svg" />
</picture>
</a>
<p align="center">
<a href="https://stytch.com/?utm_source=oss-sponsorship&utm_medium=paid_sponsorship&utm_campaign=xmlcrypto">
<b>The identity platform for humans & AI agents</b><br/>
One integration for authentication, authorization, and security
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add alt text and drop unsupported width on <source> for better accessibility & spec-compliance

  • MD045 warns because the <img> tag has no alt attribute – screen-readers will announce nothing.
  • The width attribute is not part of the <source> element spec; it is ignored by browsers and flagged by some HTML linters.
-      <source width="200px" media="(prefers-color-scheme: dark)" srcset="./sponsor/stytch-light.svg">
-      <source width="200px" media="(prefers-color-scheme: light)" srcset="./sponsor/stytch-dark.svg">
-      <img width="200px" src="./sponsor/stytch-dark.svg" />
+      <source media="(prefers-color-scheme: dark)" srcset="./sponsor/stytch-light.svg">
+      <source media="(prefers-color-scheme: light)" srcset="./sponsor/stytch-dark.svg">
+      <img width="200px" src="./sponsor/stytch-dark.svg" alt="Stytch logo" />

This small tweak keeps the visual layout untouched while satisfying accessibility tooling and HTML semantics.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<source width="200px" media="(prefers-color-scheme: dark)" srcset="./sponsor/stytch-light.svg">
<source width="200px" media="(prefers-color-scheme: light)" srcset="./sponsor/stytch-dark.svg">
<img width="200px" src="./sponsor/stytch-dark.svg" />
</picture>
</a>
<p align="center">
<a href="https://stytch.com/?utm_source=oss-sponsorship&utm_medium=paid_sponsorship&utm_campaign=xmlcrypto">
<b>The identity platform for humans & AI agents</b><br/>
One integration for authentication, authorization, and security
<source media="(prefers-color-scheme: dark)" srcset="./sponsor/stytch-light.svg">
<source media="(prefers-color-scheme: light)" srcset="./sponsor/stytch-dark.svg">
<img width="200px" src="./sponsor/stytch-dark.svg" alt="Stytch logo" />
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

15-15: Inline HTML
Element: source

(MD033, no-inline-html)


16-16: Inline HTML
Element: source

(MD033, no-inline-html)


17-17: Inline HTML
Element: img

(MD033, no-inline-html)


17-17: Images should have alternate text (alt text)

(MD045, no-alt-text)


20-20: Inline HTML
Element: p

(MD033, no-inline-html)


21-21: Inline HTML
Element: a

(MD033, no-inline-html)


22-22: Inline HTML
Element: b

(MD033, no-inline-html)


22-22: Inline HTML
Element: br

(MD033, no-inline-html)

🤖 Prompt for AI Agents
In README.md around lines 15 to 23, the <img> tag lacks an alt attribute, which
reduces accessibility for screen readers, and the <source> elements incorrectly
use the width attribute, which is not supported. To fix this, add a meaningful
alt attribute to the <img> tag describing the image content, and remove the
width attributes from all <source> elements to comply with HTML specifications
without affecting layout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants