Product

Better your development team with shared knowledge

Do you have project-specific knowledge you’d like to share with your team? Just add code pattern and message to the rule file in your repository. Sider will let your teammates know automatically when they push code that matches the pattern.

Watch intro

Highlighted by Sider

querly.yml

rules:
  - id: com.example.app.migration_operation
    pattern:
      - create_table
    message: |
      Get ready for migration!

      Read the operation manual for DB migration.
      - https://docs.example.com/app/migrations

Highlighted by Sider

phinder.yml

- id: com.example.security.oauthToken
  pattern: "?->oauthToken()"
  message: |
    OAuth token is a credential

    Make sure to not expose the value to users or logs.
    Use `->filteredOAuthToken()` for obfuscated tokens.

Highlighted by Sider

javasee.yml

- id: java.date
  pattern:
        - new Date(...)
  message: |
    We recommend not using `Date` class

    Use _Date and Time API_ introduces in Java8,
    which provides immutable and rich classes including
    `LocalDateTime` and `ZonedDateTime`.

Highlighted by Sider

tyscan.yml

- id: anchor_without_href
  pattern: '<a !href>'
  message: |
    Try using `Button` component instead of an anchor

    When you want a button, which responds to users' click,
    please use `Button` component.
    An `a` tag should only be used for navigations between URLs.

Highlighted by Sider

goodcheck.yml

rules:
  - id: review.sider.wording.signin
    pattern:
      - token: Log in
        case_sensitive: false
      - token: Log out
        case_sensitive: false
    glob: 
      - "**/*.html.erb"
      - "**/*.yml"
    message: |
      Please use “sign in”/“sign out”

      We use “sign in” instead of “log in” and “sign out” instead of “log out”.
      See the wording policy for details.

      https://docs.example.com/1840
    fail:
      - "Log in"
      - "Log out"
    pass:
      - "Sign in"
      - "Sign out"

See more tools

Choose the tools that are right for you

Pick the best tools for your project from Querly, Phinder, JavaSee, and TyScan, depending on the language of your choice. These tools use expressive pattern language based on programming language syntax, making it possible to detect code pieces with precision. You can also make use of Goodcheck, which is based on regular expressions and lets you write rules for any and all text files.

Querly

Ruby

GitHub Tutorial

Phinder

PHP

GitHub Tutorial

Goodcheck

General

GitHub Tutorial

JavaSee

Java

GitHub

TyScan

TypeScript

GitHub

Read how other teams benefitted from custom tools

Sider goes beyond reminders - easily create rules and alerts for code errors.

Read full story

Querly is a useful code analysis tool that helps us effectively share project rules.

Read full story

Read all customer stories

Seamless GitHub integration

Supercharge your workflow with Sider

CODE
PULL
Sider
FIX
MERGE

1. Make amendments to your project

Work as you would normally, coding changes to your existing GitHub project.

2. Create new pull request

Sider will automatically analyze your pull request, ignoring the unchanged parts, so you can focus on your developing code.

3. Sider reviews your pull request

You'll receive your code review results as a merging status in your pull request, so you won't miss it.

4. Check the issues and fix them

Review reported issues on Sider. Fix or close the issues, and push the new commit.

5. Merge and deploy

Now that the issues found by Sider have been resolved, ask your teammates to review and approve your code for deployment.

Popular analysis tools support
Sider supports over 20 tools to help developers follow industry standards for high quality code.
Security
Analysis tools run in isolated environments; one off Docker container for each analysis session.
Test Mode
Run initial setup and adjust config settings with test mode. Your project won’t be affected during your trial-and-error.
Customization as usual
Sider offers great customization flexibility. Import your existing analyzer configs to tailor fit your needs.
Default Configuration
Your repositories will be ready for analysis as soon as you select them. Use our default configuration to get immediate results.
Slack Integration
Keep up to date with analysis results with Slack integration. Automatically be notified of continuous analysis results.
In-house Support
In-house support will address any of your issues, config or otherwise. Never hesitate to contact us.
Easy Debugging
Analysis logs are made available for each tool for each analysis, when debugging is necessary.
GitHub Permissions Integration
Access settings are imported from GitHub automatically. Start immediately without worrying about setting permissions.

Watch our tutorials

Watch our tutorials to learn more about Sider’s functionality, set-ups, and tricks to speed up your workflow.

See all tutorials

Try Sider for free

Free 14-day trial for private repositories, and forever free for open source.
Sign up before October 31st for standard or enterprise plan and have your free trial extended to 3 months! No credit card required.

Signup via GitHub for free