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

OpenSFF Best Practices Badge Program for Dashboard #2429

Closed
afrittoli opened this issue Aug 31, 2022 · 3 comments · Fixed by #2510
Closed

OpenSFF Best Practices Badge Program for Dashboard #2429

afrittoli opened this issue Aug 31, 2022 · 3 comments · Fixed by #2510
Assignees
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@afrittoli
Copy link
Member

Achieve the OpenSFF Best Practices Badge.
Add the badge to the main project README.

@afrittoli
Copy link
Member Author

FYI @tektoncd/dashboard-maintainers - anyone available to drive this to completion?

@afrittoli afrittoli moved this to In Progress in Tekton Graduation Oct 2, 2022
@afrittoli
Copy link
Member Author

CII Best Practices

@AlanGreene
Copy link
Member

AlanGreene commented Oct 4, 2022

Remaining sections:

  • Basics
    • The project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project.

      We have documentation for the Dashboard API + extensions, and the getting started tutorial describes the core features of the UI. Is this sufficient?

  • Quality
  • Analysis
    • PR open to add CodeQL Enable CodeQL analysis #2508, this should satisfy the static code analysis items
    • the remaining items in dynamic code analysis are then either N/A or unmet (but only suggested, e.g. fuzzing)

That should get us to 100% 🤞

Repository owner moved this from In Progress to Done in Tekton Graduation Oct 4, 2022
Repository owner moved this from Todo to Done in Tekton Community Roadmap Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
Status: Done
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants