HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mozilla
addons-linter
JavaScript2016–2023
mozilla / addons-linter

addons-linter

🔍 Firefox Add-ons linter, written in JavaScript. 👁

8Distinct people
10Mentions
0Explicit recommenders
366GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

🔍 Firefox Add-ons linter, written in JavaScript. 👁

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, 3:03:16 PM 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 year10 dated mentions

Observed mentions: 2016-10-20 17:17:34 UTC to 2023-03-14 19:13:43 UTC.

024682016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023

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
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC817
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC211

What Hacker News says

10 sources
tldr; I've made a PR for Mozilla addons-linter and want it to have more visibility for the Mozilla team, so I ask you to make an interaction with the original issue. --- A while back I've made what-to-click (https://addons.mozilla.org/firefox/addon/what-to-click/) -- an extension for Firefox that let's you create step-by-step documentation from recording your page clicks. Each step is added to a guide with a basic pre-generated message and a screenshot. It's working pretty well, but one glaring issue is that it doesn't have any way to edit the screenshots, which may contain sensitive information. This prevents usage in some cases, especially when trying to generate a document for general public where each identifiable information may turn problematic to the creator. Since this is my side-project, and also I want to keep it as simple (yet
Read the rest
precise) as possible, so rather than creating a small Paint clone, I tackled the anonymisation with help of tesseract.js. In short, for each screenshot, OCR finds words and boxes those fit into. For each box I create a button that toggles scrubbing. I can't imagine anything simpler, yet precise for the end-user to edit the screenshot. You can see it in action here: https://www.youtube.com/watch?v=2RIWDiZ8X04 . It's good enough, sometimes it misses words written in less contrast colours, but that's a trade-off between OCR analysis speed and precision I'm willing to take. The problem is that, since I want to keep the extension fully offline, I have to have tesseract's implementation included into my extension. Since tesseract is using WASM, the resulting files are quite big, since those contain binaries that will run heavy loads efficiently. Those big files are making Firefox addon portal linter throw an error when I try to submit the new version. Linter allows max. 4MB files, but the largest one in the project is 4.8MB. With this error I can't proceed with the submission. The suggestion is to split the file into smaller ones, however I don't see a way of doing so for the WASM module and the way tesseract is loading this file. If you see any way of splitting the file, please let me know, the code can be found here: https://github.com/wrbl606/what-to-click . Since all my attempts of splitting the file failed (can't use import/export to join files in the runtime, can't access the blob in the window element), I've created an issue following with fixing PR for the addons-linter from Mozilla, that will bump max. single file size to 5MB instead of currently used 4MB. The 4MB limit was set in 2016 and is getting a bit outdated since WASM modules must contain the binary blob afaik, and blocking extensions with WASM modules in them will make us miss many exicting projects in the future (or maybe even in the past, don't really know how many devs already abandoned projects for Firefox because of this limitation). So, in short, since I don't have any response from Mozilla on my PR, I wanted to ask you to leave a comment or an emote on the original issue for better visibility for the Mozilla team. The issue can be found here: https://github.com/mozilla/addons-linter/issues/4748 . Thanks in advance <3
In Mozilla, please let me in:'( what-to-click extension update with AI stuff
Note that the Angular team is working with Mozilla and the researcher on this (see https://github.com/mozilla/addons-linter/issues/1000#issueco...) and that NDAs are a real, if insane, thing still to this day, and there is literally no way to legally compel any party to admit to being under NDA except in a court of law. Should the researcher have told the Angular team? Yes. Should they have told the entire world? Probably no. Should Mozilla tell the world? Probably even less no. As long as the parties are talking (which they are), this is an unfinished security review on lock-down to prevent exploitation in the interrim.
In Angular 1.x Banned from Firefox Addons
So, there's so many problems with this i don't know where to begin. Since folks have already noted the "not notifying google" issue, let me point out another: Prior to banning, i can find literally no discussion or details about this being about to happen (IE no notice), pretty much ever. You can see it was initially noted here: https://github.com/mozilla/addons-linter/commit/86f4dfb44355... I can find no discussion around it (maybe it's there but i'm missing it? I looked in a lot of places). You can see it fixed an issue to "warn third party developers of things we banned/don't advise", but there's nothing about initially banning anything there, and it was added with an initial ban list containing angular. I would have expected a page added, then a ban discussed, then a ban added. or something. In fact, the details of the ban changed
Read the rest
(https://github.com/mozilla/addons-linter/commit/2dcc2226e2ec...) repeatedly without notice either. This seems really bad. I would have expected, at the very least, a heads up to extension developers or something or even a more public notice when it happened so that some discussion could be had about it. Instead, it looks like the only way you would have found out about it is by trying to lint an extension and see it banned (IE after you developed it), or somehow random browsing of doc pages mozilla has.
In Angular 1.x Banned from Firefox Addons

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.