HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
lunasec-io
lunasec
TypeScript2021–2024
lunasec-io / lunasec

lunasec

LunaSec - Dependency Security Scanner that automatically notifies you about vulnerabilities like Log4Shell or node-ipc in your Pull Requests and Builds. Protect yourself in 30 seconds with the LunaTrace GitHub App: https://github.com/marketplace/lunatrace-by-lunasec/

4Distinct people
39Mentions
1Explicit recommenders
1.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

LunaSec - Dependency Security Scanner that automatically notifies you about vulnerabilities like Log4Shell or node-ipc in your Pull Requests and Builds. Protect yourself in 30 seconds with the LunaTrace GitHub App: https://github.com/marketplace/lunatrace-by-lunasec/

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

Nit picking a bit but I prefer btrfs even if it's slower. Easier to work with. What bootloader is this using? Or is it just straight EFI booting? I helped write a guide a few…

freeqaz used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:17:24 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 year39 dated mentions

Observed mentions: 2021-11-01 15:24:34 UTC to 2024-09-14 21:35:23 UTC.

05101520252021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 10 mentions; 2 submissions, 8 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 24 mentions; 1 submissions, 23 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

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
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1028
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC24123
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC404
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

10 sources
We couldn't figure out the actual network bypass for this one, so it's not included in the post (even though it's in the CVE). It's gotta be in this function[0] though, and if you have any notes we'd appreciate if you shared any notes with us! Edit: I spoke too soon! As we were writing this, somebody on Twitter figured it out[2]. Also, we just released v1.4 of the Log4Shell CLI tool for detecting + patching this vuln. Feel free to check that out on GitHub[1]. It's got a ton of improvements from the last release. 0: https://github.com/apache/logging-log4j2/blob/master/log4j-c... 1: https://github.com/lunasec-io/lunasec/releases/ 2: https://twitter.com/marcioalm/status/1471740771581652995
In Log4Shell Update: Full bypass found in log4j 2.15.0, enabling RCE again
log4j-api isn't actually a problem (directly). It's the usage of log4j-core that has the JndiManager class that's the injection point for RCE. In the case of the transient dependency, it's further complicated because we've seen that some packages repackage the JARs they depend on... that means that statically analyzing for log4j is very difficult because you can't use hashes (even if you unzip the jar and hash class files directly). I've been working on a scanner for this stuff on GitHub[0], and it's a real pain in the neck lol. Especially for Vendor software that you don't control. 0: https://github.com/lunasec-io/lunasec/tree/master/tools/log4...
In Log4j 2.15.0 – Previously suggested mitigations may not be enough
It uses the Log4Shell exploit to load some Java bytecode (read through this[0] blog post for context on Log4Shell). Then, once it loads that code, it scans the memory of the system and rewrites the various log4j classes that are loaded in memory. The code for that is this[1] Java file. There is a good talk on JNDI exploits in that[0] blog post if you want more details. :) 0: https://www.lunasec.io/docs/blog/log4j-zero-day/#how-the-exp... 1: https://github.com/lunasec-io/lunasec/blob/master/tools/log4...
In Log4Shell update: second Log4j vulnerability published
We also wrote a Log4Shell payload that will in-memory "hot patch" your server against Log4Shell. ${jndi:ldap://hotpatch.log4shell.com:1389/a} If you paste that into a vulnerable server (or even throw it into a log statement in your `main` function), that'll patch you against this until you can manage to update properly. Source code is on GitHub here[0][1] if you want to host it yourself. (This work is based on Logout4Shell[2], but we rewrote it to fix the bugs, make it work in more places, and also hosted it so that you don't have to muck with DNS and live server stuff.) 0: https://github.com/lunasec-io/lunasec/releases/ 1: (Go source code) https://github.com/lunasec-io/lunasec/tree/master/tools/log4... 2: https://github.com/Cybereason/Logout4Shell
In Log4Shell update: second Log4j vulnerability published
freeqaz·Nov 23, 2021Submission

Ask HN: Best way to get feedback from developers?

I've been working on an Open Source project[0] recently, and I've been wondering about the best way to actually talk with developers. I'm a dev. I don't really like to talk to people unless I have to. Getting me on the phone for 15 minutes with a stranger... is unlikely. Even with a $20 gift card incentive. I presume most other devs are the same. So, what's the best way to talk with devs and gather meaningful feedback to be able to improve the project? I want to know answers to questions like, "Would you use this? If not, why not?" or "After reading the docs, can you explain back to me what the project does for you?" Maybe HN isn't the place to ask this. Maybe this is too business focused. But, I figured I'd ask anyway. What ideas do you have for how an Open Source project could gather feedback from you? It's a very good way to "give back
Read the rest
" to Open Source, so maybe that's the best angle to take? Thanks! 0: https://github.com/lunasec-io/lunasec
3 points · Open discussion
I really can't emphasize this enough. I work with a small team (2 other devs) and our morning standup happens 3x per week. We're remote and we're building Open Source tech[0]. We do it similarly to how you describe here -- we have a short intro (5 mins) before diving into each of us presenting. Each of us presenting may take 2 mins or take 30 mins. If one of us is struggling or blocked, we use this time to collaborate + pair program/debug. Eventually, we get through everything and then go about our day. Sometimes (because I am the "lead"), I'll use the opportunity to ask questions about roadmap or other items that I need their input on. They're already distracted and not "in the zone", so chaining on the additional "meeting" works quite well. Because of this, these are our only meetings every week. We get a bit of "water cooler" chatting
Read the rest
in, we are able to unblock each other, and we are able to have a short iteration loop for re-prioritizing our work. (New tasks can be delegated by quickly going through the backlog) The pandemic has really changed work, and I really feel like we're still iterating on what the best dynamics are for teams to be productive. Thanks for the insight into your team dynamic! 0: https://github.com/lunasec-io/lunasec
In Are daily standups hurting your team?

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.