Overview
Have a look at your secure software development lifecycle posture assessment and get an overview of the risks this specific repository poses to your organization.
Security Posture
The security posture of the repository is determined by the compliance of the repository with the security policies of the organization.
All controls are passing
To-Do's
Tasks that need to be completed before the repository is ready for production, ordered by priority.
No tasks until ready
Compliance ControlsOverview
Displays the compliance of the repository with the security policies of the repository.
0 / 0 Controls are passing (NaN %)
critical severitySee all
0
By Risk. By CVSS you would have1critical severity vulnerabilities
high severitySee all
0
By Risk. By CVSS you would have9high severity vulnerabilities
medium severitySee all
7
By Risk. By CVSS you would have1medium severity vulnerabilities
low severitySee all
33
By Risk. By CVSS you would have16low severity vulnerabilities
LicensesSee all
Displays the distribution of dependency licenses
unknown
unknown, 425 dependencies
Apache-2.0
OSI Approved
Apache License 2.0, 370 dependencies
MIT
OSI Approved
MIT License, 294 dependencies
BSD-3-Clause
OSI Approved
BSD 3-Clause "New" or "Revised" License, 109 dependencies
non-standard
non-standard, 34 dependencies
MPL-2.0
OSI Approved
Mozilla Public License 2.0, 28 dependencies
BSD-2-Clause
OSI Approved
BSD 2-Clause "Simplified" License, 26 dependencies
Unlicense
OSI Approved
The Unlicense, 3 dependencies
Apache-2.0 OR MIT
Apache-2.0 OR MIT, 2 dependencies
ISC
OSI Approved
ISC License, 2 dependencies
LGPL-3.0
OSI Approved
GNU Lesser General Public License v3.0 only, 2 dependencies
MIT AND MPL-2.0
MIT AND MPL-2.0, 2 dependencies
BSD-2-Clause-Views
BSD 2-Clause with views sentence, 2 dependencies
PSF-2.0
Python Software Foundation License 2.0, 2 dependencies
Activity StreamSee all
Displays the last events that happened on the repository.
- container-scanning
- container-scanning
- container-scanning
