-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Sec1 SCA SAST Security Plugin #4087
Comments
Security audit, information and commands The security team is auditing all the hosting requests, to ensure a better security by default. This message informs you that a Jenkins Security Scan was triggered on your repository. CommandsThe bot will parse all comments, and it will check if any line start with a command. Security team only:
Anyone:
Only one command can be requested per comment. (automatically generated message, version: 1.29.12) |
Hello from your friendly Jenkins Hosting Checker It looks like you have everything in order for your hosting request. A member of the Jenkins hosting team will check over things that I am not able to check(code review, README content, etc) and process the request as quickly as possible. Thank you for your patience. Hosting team members can host this request with |
The Jenkins Security Scan did not find anything dangerous with your plugin, congratulations! 🎉 💡 The Security team recommends that you are setting up the scan in your repository by following our guide. |
can anyone update on the hosting request? |
Repository URL
https://github.com/sec0ne/secone-sca-sast-security-scanner
New Repository Name
secone-sca-sast-security-scanner-plugin
Description
The Sec1 Security plugin provides both SCA and SAST capabilities, enabling teams to scan SCM repositories for open-source vulnerabilities and analyze code to detect security issues early in development.
GitHub users to have commit permission
@rahuldarekar222
@saurabhthatte007
Jenkins project users to have release permission
rahuldarekar
saurabhthatte_sec1
Issue tracker
Jira
The text was updated successfully, but these errors were encountered: