Codeberg-e.V./requests
55
63
Fork
You've already forked requests
10

[CI] Infosec tooling, golang-based CICD access request #1897

Closed
opened 2026年05月17日 01:18:34 +02:00 by Ghost · 7 comments

Projects

Maybe more later if I have inspiration for more projects

Expected Resource Usage

minimal

I would also like the following users to be added

No response

Additional Information

I am a senior infosec dev. In addition to my day job I make tools for infosec engineers.
This project in particular stems from seeing all the infosec students download infected tools that do the same. I wish to offer a safe, clean alternative to whats out there.

Other Work

Because of the nature of my work, I'd rather not cross contaminate this profile and keep it clean. But I currently have a tool thats included in Kali Linux, and with over 550,000+ Pypi downloads.
I take infosec very seriously and firmly believe in openess.

Thank you for reading me, kind regards

Statement

  • I have placed a LICENSE file in my repository. (Or equivalent, such as COPYING or a LICENSES folder)
  • I understand that Codeberg's CI might not always be available or stable, despite best efforts.
  • I understand that I will be added to the Codeberg-CI organisation and can use the feedback repository to share feedback or report problems (email notifications for that repo are enabled by default).
### Projects - [SnowFastULP](https://codeberg.org/snoww/SnowFastULP) _Maybe more later if I have inspiration for more projects_ ### Expected Resource Usage minimal ### I would also like the following users to be added _No response_ ### Additional Information I am a senior infosec dev. In addition to my day job I make tools for infosec engineers. This project in particular stems from seeing all the infosec students download infected tools that do the same. I wish to offer a safe, clean alternative to whats out there. ### Other Work Because of the nature of my work, I'd rather not cross contaminate this profile and keep it clean. But I currently have a tool thats included in Kali Linux, and with over 550,000+ Pypi downloads. I take infosec very seriously and firmly believe in openess. Thank you for reading me, kind regards ### Statement - [x] I have placed a LICENSE file in my repository. (Or equivalent, such as `COPYING` or a [LICENSES folder](https://reuse.software)) - [x] I understand that Codeberg's CI might not always be available or stable, despite best efforts. - [x] I understand that I will be added to the [Codeberg-CI organisation](https://codeberg.org/Codeberg-CI/) and can use the [feedback repository](https://codeberg.org/Codeberg-CI/feedback) to share feedback or report problems (email notifications for that repo are enabled by default).

The following projects likely have a non-approved license:

  • SnowFastULP: PolyForm-Noncommercial-1.0.0 (confidence: 0.99)

The following projects do not have enough activity:

Not qualified for auto-approval.
If you believe this to be an error, please wait until a human reviewer takes a look at your request.
You do not need to open another request.

The following projects likely have a non-approved license: - [SnowFastULP](https://codeberg.org/snoww/SnowFastULP): PolyForm-Noncommercial-1.0.0 (confidence: 0.99) The following projects do not have enough activity: - [SnowFastULP](https://codeberg.org/snoww/SnowFastULP) Not qualified for auto-approval. If you believe this to be an error, please wait until a human reviewer takes a look at your request. You do not need to open another request.

Yeah a collegue recommended that licence, shoulda stuck to GPL.

Yeah a collegue recommended that licence, shoulda stuck to GPL.

If you change the license to GPL, we would definitely approve the CI access.
I am currently asking the CI team regarding the PolyForm-Noncommercial-1.0.0.

If you change the license to GPL, we would definitely approve the CI access. I am currently asking the CI team regarding the PolyForm-Noncommercial-1.0.0.

Hey @martins-avots thanks for the answer. I just really want to lock in a licence that protects the project(s) from becoming for-profit.
I've had it happen to a previous project, which is probably why I am a bit salty. Thank you

Hey @martins-avots thanks for the answer. I just really want to lock in a licence that protects the project(s) from becoming for-profit. I've had it happen to a previous project, which is probably why I am a bit salty. Thank you
Member
Copy link

One of the pillars of Free/Libre Open Source Software is that there is no difference made between those who get your software; everybody who gets your software should be able to use it however they wish. This includes using the software in a for-profit context.

If you are worried about everybody being on a level playing field, you can use a license like AGPL. That would mean that, if someone takes your software, modifies it, and then distributes that further, making a profit from that, then you can take back the changes into your project and pursue making a profit yourself.

If you indeed want for-profit usage of your software to be prohibited, then that unfortunately means that your software is not F/LOSS.

One of the pillars of Free/Libre Open Source Software is that there is no difference made between those who get your software; everybody who gets your software should be able to use it however they wish. This includes using the software in a for-profit context. If you are worried about everybody being on a level playing field, you can use a license like AGPL. That would mean that, if someone takes your software, modifies it, and then distributes that further, making a profit from that, then you can take back the changes into your project and pursue making a profit yourself. If you indeed want for-profit usage of your software to be prohibited, then that unfortunately means that your software is not F/LOSS.

@snoww Unfortunately, we came to the conclusion, that PolyForm-Noncommercial-1.0.0 is not fitting Codeberg's licensing criteria for CI.

@snoww Unfortunately, we came to the conclusion, that PolyForm-Noncommercial-1.0.0 is not fitting Codeberg's licensing criteria for CI.

Hello @kbruen and @martins-avots 👋
I believe the looming risk of having a passion project become a cogwheel to a mercantile dynamic does not pass my personal vibe check. Which is fine, and also personal.
Thank you for the thoughful replies and having taken the time to review my request. I guess this is the part where I will respectfully discontinue and invoke GDPR article 17's right to erasure please.
I wish you all the best 🌈

  • Snow
Hello @kbruen and @martins-avots 👋 I believe the looming risk of having a passion project become a cogwheel to a mercantile dynamic does not pass my personal vibe check. Which is fine, and also personal. Thank you for the thoughful replies and having taken the time to review my request. I guess this is the part where I will respectfully discontinue and invoke GDPR article 17's right to erasure please. I wish you all the best 🌈 - Snow
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg-e.V./requests#1897
Reference in a new issue
Codeberg-e.V./requests
No description provided.
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?