HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
github
super-linter
Shell2020–2020
github / super-linter

super-linter

Combination of multiple linters to install as a GitHub Action

7Distinct people
8Mentions
0Explicit recommenders
158GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Combination of multiple linters to install as a GitHub Action

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval8 dated mentions

Observed mentions: 2020-06-18 16:07:25 UTC to 2020-06-21 18:05:59 UTC.

0123452020-06-18 15:00:00 UTC to 2020-06-18 18:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 commentsJun 18, 15:002020-06-18 18:00:00 UTC to 2020-06-18 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-06-18 21:00:00 UTC to 2020-06-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 00:00:00 UTC to 2020-06-19 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 03:00:00 UTC to 2020-06-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 06:00:00 UTC to 2020-06-19 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 09:00:00 UTC to 2020-06-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 12:00:00 UTC to 2020-06-19 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2020-06-19 15:00:00 UTC to 2020-06-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 18:00:00 UTC to 2020-06-19 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-19 21:00:00 UTC to 2020-06-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-20 00:00:00 UTC to 2020-06-20 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-20 03:00:00 UTC to 2020-06-20 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 20, 03:002020-06-20 06:00:00 UTC to 2020-06-20 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-20 09:00:00 UTC to 2020-06-20 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-20 12:00:00 UTC to 2020-06-20 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-20 15:00:00 UTC to 2020-06-20 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-20 18:00:00 UTC to 2020-06-20 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-20 21:00:00 UTC to 2020-06-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 00:00:00 UTC to 2020-06-21 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 03:00:00 UTC to 2020-06-21 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 06:00:00 UTC to 2020-06-21 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 09:00:00 UTC to 2020-06-21 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 12:00:00 UTC to 2020-06-21 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 15:00:00 UTC to 2020-06-21 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-21 18:00:00 UTC to 2020-06-21 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 21, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 18, 15:002020-06-18 15:00:00 UTC2020-06-18 18:00:00 UTC505
Jun 18, 18:002020-06-18 18:00:00 UTC2020-06-18 21:00:00 UTC101
Jun 18, 21:002020-06-18 21:00:00 UTC2020-06-19 00:00:00 UTC000
Jun 19, 00:002020-06-19 00:00:00 UTC2020-06-19 03:00:00 UTC000
Jun 19, 03:002020-06-19 03:00:00 UTC2020-06-19 06:00:00 UTC000
Jun 19, 06:002020-06-19 06:00:00 UTC2020-06-19 09:00:00 UTC000
Jun 19, 09:002020-06-19 09:00:00 UTC2020-06-19 12:00:00 UTC000
Jun 19, 12:002020-06-19 12:00:00 UTC2020-06-19 15:00:00 UTC110
Jun 19, 15:002020-06-19 15:00:00 UTC2020-06-19 18:00:00 UTC000
Jun 19, 18:002020-06-19 18:00:00 UTC2020-06-19 21:00:00 UTC000
Jun 19, 21:002020-06-19 21:00:00 UTC2020-06-20 00:00:00 UTC000
Jun 20, 00:002020-06-20 00:00:00 UTC2020-06-20 03:00:00 UTC000
Jun 20, 03:002020-06-20 03:00:00 UTC2020-06-20 06:00:00 UTC000
Jun 20, 06:002020-06-20 06:00:00 UTC2020-06-20 09:00:00 UTC000
Jun 20, 09:002020-06-20 09:00:00 UTC2020-06-20 12:00:00 UTC000
Jun 20, 12:002020-06-20 12:00:00 UTC2020-06-20 15:00:00 UTC000
Jun 20, 15:002020-06-20 15:00:00 UTC2020-06-20 18:00:00 UTC000
Jun 20, 18:002020-06-20 18:00:00 UTC2020-06-20 21:00:00 UTC000
Jun 20, 21:002020-06-20 21:00:00 UTC2020-06-21 00:00:00 UTC000
Jun 21, 00:002020-06-21 00:00:00 UTC2020-06-21 03:00:00 UTC000
Jun 21, 03:002020-06-21 03:00:00 UTC2020-06-21 06:00:00 UTC000
Jun 21, 06:002020-06-21 06:00:00 UTC2020-06-21 09:00:00 UTC000
Jun 21, 09:002020-06-21 09:00:00 UTC2020-06-21 12:00:00 UTC000
Jun 21, 12:002020-06-21 12:00:00 UTC2020-06-21 15:00:00 UTC000
Jun 21, 15:002020-06-21 15:00:00 UTC2020-06-21 18:00:00 UTC000
Jun 21, 18:002020-06-21 18:00:00 UTC2020-06-21 21:00:00 UTC101

What Hacker News says

8 sources
A problem I can see with this super linter is that it seems be written exclusively for GitHub Actions; there's no local install option. (I didn't read the code, maybe you can use lib/linter.sh directly, but it's certainly not directly supported.) So contributors have to rely on the CI feedback loop to see if their changes are compliant (insert fencing comic here)... Or more realistically, still use whatever linters they've been using so far, but now you have to maintain linter configs in two places. I get why it's probably not ideal as a local tool, and integration with Status API is nice and all, but I personally prefer to see devs linting their code before pushing for review. Correction: it can run locally in Docker, as pointed out below: https://github.com/github/super-linter/blob/master/docs/run-...
In GitHub Super Linter: one linter to rule them all

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.