github-starred/awesome-sindresorhus
2
0
Fork 0
mirror of https://github.com/sindresorhus/awesome.git synced 2026-05-09 04:08:27 -05:00
Code Issues 459 Packages Projects Releases Wiki Activity

[PR #4046] [CLOSED] Add LOL / Commonly Abused #8095

New Issue
Closed
opened 2026-04-17 12:23:37 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-17 12:23:37 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/4046
Author: @danzek
Created: 3/26/2026
Status: ❌ Closed

Base: main ← Head: patch-1

📝 Commits (1)

  • 097b09d Add LOL / Commonly Abused resource link to README

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/danzek/awesome-lol-commonly-abused#readme

Living off the Land (LOL) methods, tools, and features commonly abused by attackers.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

  • Fully AI-generated pull requests are not accepted.
  • Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
  • Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
  • You have to review at least 4 other open pull requests. I've reviewed at least 7 (I may review more but will discontinue updating this PR as I've exceeded the requirement).
  1. [PR #1232] [CLOSED] Add Steem (#4019)
  • Identified linting errors
  • After submitter responded fixing previous issues, I identified another issue with missing ToC entry thru another linting error
  • Started a review because the entry name in the commit doesn't match the repo / list name exactly (unsure if this is a problem or not) and the description sounds more like a a tagline or marketing blurb IMO
  • Issued a PR for the original list repo resolving a few typos and spelling errors then indicated as such in the PR here (I did not fix the ToC issues because I suspect fixing one may result in finding more, and the submitter clearly did not resolve awesome-lint checks since these are being easily found automatically; the submitter did not follow the instructions so I left some things for the submitter to fix)
  1. [PR #1230] [CLOSED] Add Awesome Campus Ambassador (#4017)
  • I didn't find any issues. I did verify it passes lint checks and indicated I think it looks good overall. I also noted they only reviewed 2 PRs, not 4 (but perhaps this requirement increased recently?).
  1. [PR #1223] [CLOSED] Add in curated list of blockchain-related academic papers. (#4012)
  • Commented that this PR should be rejected. It is trying to replace an existing, actively-maintained repo with >16K stars with this person's own brand new repo. They'd be better off just making PRs to the repo already in the list with any changes/updates they want. I also noted that the repo didn't appear to meet the 30 days requirement when the PR was first created (but now does).
  1. [PR #1145] [CLOSED] Add Meta tags (#3955)
  • Initially I thought this looked fine and indicated as such. However, I was perusing the list later (out of personal interest as I code in both Python and Rust) and noticed there is an unmaintained project in the list. I commented so and also expressed my thoughts on a section listed in the ToC that is not really part of the list itself for consideration. I also noticed only 2 PRs were reviewed (was this recently increased to 4?).
  1. [PR #1260] [MERGED] Add macOS Open Source Apps (#4040)
  • This repo was only created a couple days ago so doesn't meet the minimum 30 days' age requirement. I commented indicating this.
  1. [PR #1077] [MERGED] Fix spelling (#3894)
  • This list contains an unmaintained item (archived repo). I commented indicating this.
  1. [PR #1084] [MERGED] Add Cryptography Papers (#3901)

  • URL in commit does not end in #readme so I initiated a review.

  • I also noted the unnecessary nesting in the ToC and that the project logo is not linked to the website.

  • You have read and understood the instructions for creating a list.

  • This pull request has a title in the format Add Name of List. It should not contain the word Awesome.

    • ✅ Add Swift
    • ✅ Add Software Architecture
    • ❌ Update readme.md
    • ❌ Add Awesome Swift
    • ❌ Add swift
    • ❌ add Swift
    • ❌ Adding Swift
    • ❌ Added Swift

  • Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.

    • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
    • ✅ - [Framer](…) - Prototyping interactive UI designs.
    • ❌ - [iOS](…) - Resources and tools for iOS development.
    • ❌ - [Framer](…)
    • ❌ - [Framer](…) - prototyping interactive UI designs

  • Your entry should be added at the bottom of the appropriate category.

  • The title of your entry should be title-cased and the URL to your list should end in #readme.

    • Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

  • No blockchain-related lists.

  • The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

  • Has been around for at least 30 days.
    That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  • Is not AI-generated.
  • Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
  • The default branch should be named main, not master.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
    • ✅ Mobile operating system for Apple phones and tablets.
    • ✅ Prototyping interactive UI designs.
    • ❌ Resources and tools for iOS development.
    • ❌ Awesome Framer packages and tools.
  • It's the result of hard work and the best I could possibly produce.
    If you have not put in considerable effort into your list, your pull request will be immediately closed.
  • The repo name of your list should be in lowercase slug format: awesome-name-of-list.
    • ✅ awesome-swift
    • ✅ awesome-web-typography
    • ❌ awesome-Swift
    • ❌ AwesomeWebTypography
  • The heading title of your list should be in title case format: # Awesome Name of List.
    • ✅ # Awesome Swift
    • ✅ # Awesome Web Typography
    • ❌ # awesome-swift
    • ❌ # AwesomeSwift
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
  • Not a duplicate. Please search for existing submissions.
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
  • Includes a project logo/illustration whenever possible.
    • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
    • The image should link to the project website or any relevant website.
    • The image should be high-DPI. Set it to a maximum of half the width of the original image.
    • Don't include both a title saying Awesome X and a logo with Awesome X. You can put the header image in a # (Markdown header) or <h1>.
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Includes the Awesome badge.
    • Should be placed on the right side of the readme heading.
      • Can be placed centered if the list has a centered graphics header.
    • Should link back to this list.
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
    • Should only have one level of nested lists, preferably none.
    • Must not feature Contributing or Footnotes sections.
  • Has an appropriate license.
    • We strongly recommend the CC0 license, but any Creative Commons license will work.
      • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
    • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
    • Place a file named license or LICENSE in the repo root with the license text.
    • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
    • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
  • Has contribution guidelines.
    • The file should be named contributing.md. The casing is up to you.
    • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
    • The section should not appear in the Table of Contents.
  • All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
  • Has consistent formatting and proper spelling/grammar.
    • The link and description are separated by a dash.
      Example: - [AVA](…) - JavaScript test runner.
    • The description starts with an uppercase character and ends with a period.
    • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
  • Does not use hard-wrapping.
  • Does not include a CI (e.g. GitHub Actions) badge.
    You can still use a CI for linting, but the badge has no value in the readme.
  • Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/4046 **Author:** [@danzek](https://github.com/danzek) **Created:** 3/26/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`097b09d`](https://github.com/sindresorhus/awesome/commit/097b09dad194446102556429b22ed1b748aabbbc) Add LOL / Commonly Abused resource link to README ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description **https://github.com/danzek/awesome-lol-commonly-abused#readme** Living off the Land (LOL) methods, tools, and features commonly abused by attackers. ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 ## Requirements for your pull request - [X] Fully AI-generated pull requests are not accepted. - [X] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. **Instead use [#2242](https://github.com/sindresorhus/awesome/issues/2242) for incubation visibility**. - [X] **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive. - [X] **You have to review at least 4 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** I've reviewed _at least_ 7 (I may review more but will discontinue updating this PR as I've exceeded the requirement). 1. #4019 - [Identified](https://github.com/sindresorhus/awesome/pull/4019#issuecomment-4137326531) linting errors - After submitter responded fixing previous issues, I [identified](https://github.com/sindresorhus/awesome/pull/4019#issuecomment-4139239875) another issue with missing ToC entry thru another linting error - [Started a review](https://github.com/sindresorhus/awesome/pull/4019/changes/BASE..f506a3ebd9f10b642c9f36867c4aeaf230628a9a#r2998507217) because the entry name in the commit doesn't match the repo / list name exactly (unsure if this is a problem or not) and the description sounds more like a a tagline or marketing blurb IMO - [Issued a PR for the original list repo](https://github.com/Smithech/awesome-hacking-training/pull/1) resolving a few typos and spelling errors then [indicated as such in the PR here](https://github.com/sindresorhus/awesome/pull/4019#issuecomment-4139438937) (I did not fix the ToC issues because I suspect fixing one may result in finding more, and the submitter clearly did not resolve `awesome-lint` checks since these are being easily found automatically; the submitter did not follow the instructions so I left some things for the submitter to fix) 2. #4017 - I didn't find any issues. I did verify it passes lint checks and [indicated](https://github.com/sindresorhus/awesome/pull/4017#issuecomment-4137345844) I think it looks good overall. I also noted they only reviewed 2 PRs, not 4 (but perhaps this requirement increased recently?). 3. #4012 - [Commented](https://github.com/sindresorhus/awesome/pull/4012#issuecomment-4137369490) that this PR should be rejected. It is trying to replace an existing, actively-maintained repo with >16K stars with this person's own brand new repo. They'd be better off just making PRs to the repo already in the list with any changes/updates they want. I also noted that the repo didn't appear to meet the 30 days requirement when the PR was first created (but now does). 4. #3955 - Initially I thought this looked fine and [indicated as such](https://github.com/sindresorhus/awesome/pull/3955#issuecomment-4137393089). However, I was perusing the list later (out of personal interest as I code in both Python and Rust) and noticed there is an unmaintained project in the list. [I commented so](https://github.com/sindresorhus/awesome/pull/3955#issuecomment-4139664424) and also expressed my thoughts on a section listed in the ToC that is not really part of the list itself for consideration. I also noticed only 2 PRs were reviewed (was this recently increased to 4?). 5. #4040 - This repo was only created a couple days ago so doesn't meet the minimum 30 days' age requirement. [I commented](https://github.com/sindresorhus/awesome/pull/4040#issuecomment-4139821497) indicating this. 6. #3894 - This list contains an unmaintained item (archived repo). [I commented](https://github.com/sindresorhus/awesome/pull/3894#issuecomment-4139872295) indicating this. 7. #3901 - URL in commit does not end in `#readme` so I [initiated a review](https://github.com/sindresorhus/awesome/pull/3901/changes/BASE..f8b03ed1af72865fb7e7490a51ad865dcbd96fff#r2998792861). - [I also noted](https://github.com/sindresorhus/awesome/pull/3901#issuecomment-4139934626) the unnecessary nesting in the ToC and that the project logo is not linked to the website. - [X] You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md). - [X] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`. - ✅ `Add Swift` - ✅ `Add Software Architecture` - ❌ `Update readme.md` - ❌ `Add Awesome Swift` - ❌ `Add swift` - ❌ `add Swift` - ❌ `Adding Swift` - ❌ `Added Swift` - [X] Your entry here should include a short description of the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list. - ✅ `- [iOS](…) - Mobile operating system for Apple phones and tablets.` - ✅ `- [Framer](…) - Prototyping interactive UI designs.` - ❌ `- [iOS](…) - Resources and tools for iOS development.` - ❌ `- [Framer](…)` - ❌ `- [Framer](…) - prototyping interactive UI designs` - [X] Your entry should be added at the bottom of the appropriate category. - [X] The title of your entry should be title-cased and the URL to your list should end in `#readme`. - Example: `- [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.` - [X] No blockchain-related lists. - [X] The suggested Awesome list complies with the below requirements. ## Requirements for your Awesome list - [X] **Has been around for at least 30 days.**<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent. - [X] Is not AI-generated. - [X] Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please [report it](https://github.com/sindresorhus/awesome-lint/issues/new). - [X] The default branch should be named [`main`, not `master`](https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/). - [X] **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self) - ✅ `Mobile operating system for Apple phones and tablets.` - ✅ `Prototyping interactive UI designs.` - ❌ `Resources and tools for iOS development.` - ❌ `Awesome Framer packages and tools.` - [X] It's the result of hard work and the best I could possibly produce. **If you have not put in considerable effort into your list, your pull request will be immediately closed.** - [X] The repo name of your list should be in lowercase slug format: `awesome-name-of-list`. - ✅ `awesome-swift` - ✅ `awesome-web-typography` - ❌ `awesome-Swift` - ❌ `AwesomeWebTypography` - [X] The heading title of your list should be in [title case](https://capitalizemytitle.com/) format: `# Awesome Name of List`. - ✅ `# Awesome Swift` - ✅ `# Awesome Web Typography` - ❌ `# awesome-swift` - ❌ `# AwesomeSwift` - [X] Non-generated Markdown file in a GitHub repo. - [X] The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). I encourage you to add more relevant topics. - [X] Not a duplicate. Please search for existing submissions. - [X] Only has awesome items. Awesome lists are curations of the best, not everything. - [X] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file. - [X] Includes a project logo/illustration whenever possible. - Either centered, fullwidth, or placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron) - The image should link to the project website or any relevant website. - **The image should be high-DPI.** Set it to a maximum of half the width of the original image. - Don't include both a title saying `Awesome X` and a logo with `Awesome X`. You can put the header image in a `#` (Markdown header) or `<h1>`. - [X] Entries have a description, unless the title is descriptive enough by itself. It rarely is though. - [X] Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/main/awesome.md#awesome-badge). - Should be placed on the right side of the readme heading. - Can be placed centered if the list has a centered graphics header. - Should link back to this list. - [X] Has a Table of Contents section. - Should be named `Contents`, not `Table of Contents`. - Should be the first section in the list. - Should only have one level of [nested lists](https://commonmark.org/help/tutorial/10-nestedLists.html), preferably none. - Must not feature `Contributing` or `Footnotes` sections. - [X] Has an appropriate license. - **We strongly recommend the [CC0 license](https://creativecommons.org/publicdomain/zero/1.0/), but any [Creative Commons license](https://creativecommons.org/choose/) will work.** - Tip: You can quickly add it to your repo by going to this URL: `https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0` (replace `<user>` and `<repo>` accordingly). - A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and [Unlicense](https://unlicense.org). - Place a file named `license` or `LICENSE` in the repo root with the license text. - **Do not** add the license name, text, or a `Licence` section to the readme. GitHub already shows the license name and link to the full text at the top of the repo. - To verify that you've read all the guidelines, please comment on your pull request with just the word `unicorn`. - [X] Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/main/awesome.md#include-contribution-guidelines). - The file should be named `contributing.md`. The casing is up to you. - It can optionally be linked from the readme in a dedicated section titled `Contributing`, positioned at the top or bottom of the main content. - The section should not appear in the Table of Contents. - [X] All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a `Footnotes` section at the bottom of the readme. The section should not be present in the Table of Contents. - [X] Has consistent formatting and proper spelling/grammar. - The link and description are separated by a dash. <br>Example: `- [AVA](…) - JavaScript test runner.` - The description starts with an uppercase character and ends with a period. - Consistent and correct naming. For example, `Node.js`, not `NodeJS` or `node.js`. - [X] Does not use [hard-wrapping](https://stackoverflow.com/questions/319925/difference-between-hard-wrap-and-soft-wrap). - [X] Does not include a CI (e.g. GitHub Actions) badge.<br>You can still use a CI for linting, but the badge has no value in the readme. - [X] Does not include an `Inspired by awesome-foo` or `Inspired by the Awesome project` kinda link at the top of the readme. The Awesome badge is enough. **Go to the top and read it again.** --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-17 12:23:37 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
help wanted
invalid
list request
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#8095
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?