{% extends "bases/base.tera.html" %} {% block title %} {% if section.title %} {{ section.title }} {% else %} Hipcheck {% endif %} {% endblock %} {% block body_classes %} {% endblock %} {# Turn off breadcrumbs for the index page. #} {% block breadcrumbs %}{% endblock %} {% block content %} Identify risky practices and possible attacks in your software dependencies. {% include "partials/install.tera.html" %} {{ ic::icon(name="book", classes="!w-5 !h-5 mt-[-2px] mr-1") }} Read the Docs {% endblock %} {% block sidebar %}
Analyzing
{{ ic::icon(name="link") }}
pkg:github/example/project
{{ ic::icon(name="box") }} mitre/activity
Is the project maintained? Active. Last commit 7 days ago.
{{ ic::icon(name="check", classes="fill-green-800") }} Pass 50% weight
{{ ic::icon(name="box") }} mitre/review
Are there code reviews? Code reviews common on PRs
{{ ic::icon(name="check", classes="fill-green-800") }} Pass 30% weight
{{ ic::icon(name="box") }} mitre/binary
Are there binaries in the repo? Warning: found prebuilt, prebuilt.exe
{{ ic::icon(name="alert-circle", classes="fill-yellow-800") }} Investigate 20% weight
0.2 Risk Score is ≤ 0.5 Risk Policy so {{ ic::icon(name="check", classes="") }} Pass Result
{% endblock %} {% block extra %}

Maintainers don't need drive-by comments with best practice scanner results, they need insights to make dependencies work for them.

We’re not building Yet Another Analysis Tool, we’re building an analysis swiss army knife you can extend, modify, and own.

Hipcheck’s plugin system means anyone can add new data sources and analyses, and users control what runs and what gets recommended.

We wear our values on our sleeves, and we’re proud to be working for regular maintainers.

{% endblock %}