Skip to content

Conversation

Stephan202
Copy link
Member

@Stephan202 Stephan202 commented Apr 16, 2023

Suggested commit message:

Add additional quality badges to README (#584)

Check this link to see what it would look like on the home page. I considered other orders/formatting, but none looked obviously better. Let's merge #575 before we merge this PR.

W.r.t. whether to show multiple SonarCloud badges: I opted for "yes", as it does concisely summarize the various dimensions along which we achieved high quality.

@Stephan202 Stephan202 added this to the 0.10.0 milestone Apr 16, 2023
@Stephan202 Stephan202 requested review from japborst and rickie April 16, 2023 09:33
@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@Stephan202 Stephan202 force-pushed the sschroevers/more-badges branch 3 times, most recently from 7e3fb68 to d5ae35e Compare April 16, 2023 09:51
@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

3 similar comments
@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link
Member

@japborst japborst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think formatting is fine and separate badges make sense. Was there any particular reasoning for the ordering?

[openssf-best-practices-badge]: https://bestpractices.coreinfrastructure.org/projects/7199/badge
[openssf-best-practices-checklist]: https://bestpractices.coreinfrastructure.org/projects/7199
[openssf-scorecard-badge]: https://img.shields.io/ossf-scorecard/github.com/PicnicSupermarket/error-prone-support?label=openssf%20scorecard
[openssf-scorecard-report]: https://api.securityscorecards.dev/projects/github.com/PicnicSupermarket/error-prone-support
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a better link that has a UI? As this returns JSON. (Have personally not seen this on other projects, so not sure what's common here)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was wondering the same thing, but modeled this after what the authors do themselves. It looks like so far there was no effort to build a proper UI. (A subset of the findings are reported here, but that view is not specific to OpenSSF Scorecard, and doesn't seem to be publicly accessible.)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the launch article, they mention tensorflow and flutter. Both have the badge, where tensorflow does the same as here (link to the api), whereas flutter links to https://deps.dev/project/github/flutter%2Fflutter. This is actually a nice overview!

However, searching for PicnicSupermarket/error-prone-support - although found - leads to https://deps.dev/project/github/picnicsupermarket%2Ferror-prone-support, with no info 😕

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, interesting! The Flutter page says:

Project metadata as of April 15, 2023.

Maybe it doesn't regenerate very frequently. Since we should anyway finalize #575 first, let's see what happens over the next ~48 hours 👀

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still 404... 🤷

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's unfortunate. Hoped that it would've worked in the mean time. Will approve.

Copy link
Member Author

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was there any particular reasoning for the ordering?

"A feeling" / salience. But none that I can clearly articulate 😬.

[openssf-best-practices-badge]: https://bestpractices.coreinfrastructure.org/projects/7199/badge
[openssf-best-practices-checklist]: https://bestpractices.coreinfrastructure.org/projects/7199
[openssf-scorecard-badge]: https://img.shields.io/ossf-scorecard/github.com/PicnicSupermarket/error-prone-support?label=openssf%20scorecard
[openssf-scorecard-report]: https://api.securityscorecards.dev/projects/github.com/PicnicSupermarket/error-prone-support
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was wondering the same thing, but modeled this after what the authors do themselves. It looks like so far there was no effort to build a proper UI. (A subset of the findings are reported here, but that view is not specific to OpenSSF Scorecard, and doesn't seem to be publicly accessible.)

@rickie rickie force-pushed the sschroevers/more-badges branch from d5ae35e to daf97f3 Compare April 22, 2023 14:52
@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link
Member

@rickie rickie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Made some suggestions.

README.md Outdated
[sonarcloud-security-badge]: https://sonarcloud.io/api/project_badges/measure?project=PicnicSupermarket_error-prone-support&metric=security_rating
[sonarcloud-security-master]: https://sonarcloud.io/component_measures?id=PicnicSupermarket_error-prone-support&metric=security_rating
[sonarcloud-tech-debt-badge]: https://sonarcloud.io/api/project_badges/measure?project=PicnicSupermarket_error-prone-support&metric=sqale_index
[sonarcloud-tech-debt-master]: https://sonarcloud.io/component_measures?id=PicnicSupermarket_error-prone-support&metric=sqale_index
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We write it out for the sonar things above, so let's write "technical debt", WDYT?

@rickie rickie added the documentation A documentation update label Apr 22, 2023
@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link
Member Author

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@japborst do you approve? Then we can merge it once #575 is done.

[openssf-best-practices-badge]: https://bestpractices.coreinfrastructure.org/projects/7199/badge
[openssf-best-practices-checklist]: https://bestpractices.coreinfrastructure.org/projects/7199
[openssf-scorecard-badge]: https://img.shields.io/ossf-scorecard/github.com/PicnicSupermarket/error-prone-support?label=openssf%20scorecard
[openssf-scorecard-report]: https://api.securityscorecards.dev/projects/github.com/PicnicSupermarket/error-prone-support
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still 404... 🤷

@Stephan202 Stephan202 force-pushed the sschroevers/more-badges branch from 2d40161 to 05019df Compare April 25, 2023 06:36
@Stephan202
Copy link
Member Author

Rebased; with #575 merged this PR is ready to go as well.

@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@rickie rickie merged commit 2f2e7e7 into master Apr 25, 2023
@rickie rickie deleted the sschroevers/more-badges branch April 25, 2023 06:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation A documentation update

Development

Successfully merging this pull request may close these issues.

3 participants