-
Notifications
You must be signed in to change notification settings - Fork 120
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
chore(OSSF): update branch protection to improve OSSF scorecard #780
chore(OSSF): update branch protection to improve OSSF scorecard #780
Conversation
|
✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.
|
@JamieSlome I am a fresher working in Citi and I have sent an authorization request as a Corporate Contributor for EasyCLA. Can you please approve it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Remove .env.development, package.json, package-lock.json
- I don't see any change related to branch protection.
Please revise your change.
@JamieSlome I think Branch Protection Settings can be updated by Maintainers only as we do not have access to update the settings.
I am participating in Citi hackathon, so is it fine to contribute as an individual instead of Corporate Contributor ? I guess for those who take part in hackathon needs authorization request as a Corporate Contributor, am i right ? |
Have the service report back the proxyURL for each project, rather than being embedded inside the frontend bundle. Concequence is duplicating some data but very minor and allows for us to serve different projects from different proxies in the future. Removed unused vite env var, added method to pull service's current path and substitute in the http proxy port. Works for local dev, should maintain current behaviour. Custom domain can be applied via optional config. New config value added to the config schema. Config schema documentation has been regenerated (including some other absent items).
This commit modifies the directory creation permissions in the pullRemote function of pullRemote.js. Previously, the function was setting directory permissions to 0777 (full read, write, and execute permissions for user, group, and others). This approach is not aligned with best practices for security, particularly in secure environments such as OpenShift, where overly permissive settings can lead to vulnerabilities. The updated code now sets the permissions to 0755 (read, write, and execute for the user; read and execute for group and others). This change enhances security by restricting write access to the owner only while still allowing necessary read and execute permissions.
ebbaaf6
to
368967f
Compare
Issue: Bump OSSF Score Above 9.0 ⬆️
This pull request focuses on improving the security configuration of our repository to enhance our OSSF Scorecard rating above 9.0. This involved changes in protections and access token usage.
Changes Implemented
main
branch to strengthen security, which includes:main
.main
..github
folder to enforce code ownership and ensure critical files receive proper review before merging.repo
,read:org
andread:discussion
scopes. Fine-grained tokens may not provide the required permissions.Benefits
Checklist
main
.CODEOWNERS
file to enforce ownership and improve scorecard evaluation.