Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repo Security Tab #24930

Open
pkeech opened this issue May 25, 2023 · 4 comments
Open

Repo Security Tab #24930

pkeech opened this issue May 25, 2023 · 4 comments
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@pkeech
Copy link

pkeech commented May 25, 2023

Feature Description

With the implementation of Gitea Actions, has there been discussions about creating a Security tab to display the results of commonly used security tools? For example, displaying the CVEs found from a vulnerability scan. Gitlab utilizes a security dashboard and Github uses the tab (see Screenshot).

IMHO either approach would provide benefit to the Gitea community and shouldn't be too hard to implement ... with the exception of support for specific tools reports.

Screenshots

Screenshot 2023-05-25 at 8 37 26 AM

@pkeech pkeech added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels May 25, 2023
@silverwind
Copy link
Member

silverwind commented Jun 4, 2024

Have also been looking for something like this. I think it could be done to add "Security" tab and within that a "Alerts" category along with an API to CRUD the entries that could be done during CI.

@GammaGames
Copy link

It looks like that's an enterprise feature: https://docs.gitea.com/enterprise/features/dependency-scan

image

@pkeech
Copy link
Author

pkeech commented Jun 21, 2024

@GammaGames Thanks for pointing that out. Shame that this is being locked behind the Enterprise license.

@techknowlogick
Copy link
Member

@pkeech to clarify: it's not being locked at all. there is a process that is happening to be able to contribute the functionality to the Gitea project. It was developed for a 3rd party under a contract where they are the rights holder, and the Gitea project requires that all contributions be able to fall under the DCO (similar to many other OSS projects, including the Linux Kernel). CommitGo has been fortunate that some customers are familiar with OSS and have written into the contract that the work we do for them is MIT-licensed and can be released immediately; some larger organizations have set contracts that cannot be changed (especially if trade secrets are involved as any code needs to be vetted prior to contribution to ensure that nothing sensitive is included). CommitGo is working with those customers to educate them on OSS (so in the future this will be a streamlined process) and to have the code be able to be accepted by the Gitea project.

If you (a theoretical person, not you specifically) think, "That's all nice, but you can just say that and do nothing," you can look at work CommitGo has already been able to work with folks and release such as "SAML, Azure Object Store, Max User Limitations, and many more," and that's not even everything, as the Company itself has contributed the entire initial implementation of Gitea Actions. The company has also been able to contract for PR completion and have that directly contribute to the project, and it is sponsoring several bounties for the project.

@GammaGames @herrwusel @AverageHelper ^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

4 participants