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

[OpenSSF] Complete OpenSSF Best Practices recommendations #1181

Closed
Zeitsperre opened this issue Sep 12, 2022 · 0 comments · Fixed by #2012
Closed

[OpenSSF] Complete OpenSSF Best Practices recommendations #1181

Zeitsperre opened this issue Sep 12, 2022 · 0 comments · Fixed by #2012
Assignees
Labels
standards / conventions Suggestions on ways forward
Milestone

Comments

@Zeitsperre
Copy link
Collaborator

Zeitsperre commented Sep 12, 2022

Over the past year, we have been working towards the OpenSSF Best Practices certification for xclim (https://bestpractices.coreinfrastructure.org/en/projects/6041). We are currently hovering at 88% completion, as there are still a few things that are a bit labour-intensive that need to be addressed:

  • Vulnerability Reporting Processes
    • The project MUST publish the process for reporting vulnerabilities on the project site. (URL required) Enact security policy #1604
    • If private vulnerability reports are supported, the project MUST include how to send the information in a way that is kept private. (URL required) Enact security policy #1604
    • The project's initial response time for any vulnerability report received in the last 6 months MUST be less than or equal to 14 days. (N/A)
  • Warning Flags
    • The project MUST address warnings. (Completed)
    • It is SUGGESTED that projects be maximally strict with warnings in the software produced by the project, where practical. (Completed, This was already the case, but more extensively performed in Drop Python3.8, support Pandas v2.2, reduce Warnings #1565)
  • Secure Development Knowledge
  • Dynamic Code Analysis
    • It is SUGGESTED that the project use a configuration for at least some dynamic analysis (such as testing or fuzzing) which enables many assertions. In many cases, these assertions should not be enabled in production builds. (N/A, but there certainly are cases where this kind of testing could be useful)

I would be willing to follow the Developing Secure Software training and would welcome others to do so as well (unsure of costs). Addressing these final suggestions will grant us the OpenSSF(/FAIR) software certification.

@Zeitsperre Zeitsperre added the standards / conventions Suggestions on ways forward label Sep 12, 2022
@Zeitsperre Zeitsperre self-assigned this Sep 12, 2022
@tlogan2000 tlogan2000 added this to the v0.40 milestone Sep 13, 2022
@Zeitsperre Zeitsperre modified the milestones: v0.40, v0.41 Dec 5, 2022
@Zeitsperre Zeitsperre modified the milestones: v0.41, v0.42 Feb 22, 2023
@Zeitsperre Zeitsperre modified the milestones: v0.42, v0.43 Mar 21, 2023
@Zeitsperre Zeitsperre modified the milestones: v0.43, v0.44 May 8, 2023
@Zeitsperre Zeitsperre modified the milestones: v0.44, Summer 2023 May 30, 2023
@Zeitsperre Zeitsperre modified the milestones: Summer 2023, v0.45.0 Jun 23, 2023
@Zeitsperre Zeitsperre modified the milestones: v0.45.0, v0.46.0 Sep 5, 2023
@Zeitsperre Zeitsperre modified the milestones: v0.46.0, v0.47.0 Oct 18, 2023
@Zeitsperre Zeitsperre modified the milestones: v0.47.0, v0.48.0 Nov 30, 2023
@Zeitsperre Zeitsperre changed the title Complete OpenSSF Best Practices recommendations [OpenSSF] Complete OpenSSF Best Practices recommendations Jan 17, 2024
@Zeitsperre Zeitsperre mentioned this issue Jan 17, 2024
9 tasks
@Zeitsperre Zeitsperre removed this from the v0.48.0 milestone Feb 13, 2024
@Zeitsperre Zeitsperre added this to the v0.49.0 (PyCon LT) milestone Feb 26, 2024
@Zeitsperre Zeitsperre modified the milestones: v0.49.0 (PyCon LT), v0.50.0 May 1, 2024
@Zeitsperre Zeitsperre modified the milestones: v0.50.0, Summer 2024 Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
standards / conventions Suggestions on ways forward
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants