We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To improve our score on https://securityscorecards.dev/viewer/?uri=github.com/mozilla/rhino
See https://github.com/ossf/scorecard/blob/49c0eed3a423f00c872b5c3c9f1bbca9e8aae799/docs/checks.md#signed-releases
We already publish .asc(.*) signing artifacts on Maven I think, just need to include them in Releases on Github (and update https://github.com/mozilla/rhino/blob/master/RELEASE-STEPS.md accordingly)
Also including a SLSA provenance file would be a nice bonus, upping our score from an 8 to a 10
The text was updated successfully, but these errors were encountered:
No branches or pull requests
To improve our score on https://securityscorecards.dev/viewer/?uri=github.com/mozilla/rhino
See https://github.com/ossf/scorecard/blob/49c0eed3a423f00c872b5c3c9f1bbca9e8aae799/docs/checks.md#signed-releases
We already publish .asc(.*) signing artifacts on Maven I think, just need to include them in Releases on Github (and update https://github.com/mozilla/rhino/blob/master/RELEASE-STEPS.md accordingly)
Also including a SLSA provenance file would be a nice bonus, upping our score from an 8 to a 10
The text was updated successfully, but these errors were encountered: