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

Explicit Versioning for Enhanced Security Assessments #220

Open
npennock opened this issue Feb 6, 2024 · 0 comments
Open

Explicit Versioning for Enhanced Security Assessments #220

npennock opened this issue Feb 6, 2024 · 0 comments

Comments

@npennock
Copy link

npennock commented Feb 6, 2024

The absence of clear versioning makes it difficult for users and security professionals to assess whether a specific instance of this library is affected by a reported vulnerability.

Explicit versioning is crucial for conducting comprehensive and accurate security assessments.

For instance, when a security vulnerability is identified, clear versioning allows us to determine which versions of the software are affected and need patching or updates. Without this information, users may be exposed to potential security risks unknowingly, or they may have to expend unnecessary resources to evaluate the entire codebase instead of a specific version.

Please add explicit versioning in this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant