8000 ci: apply OSSF Scorecard security best practices by UlisesGascon · Pull Request #226 · jshttp/cookie · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

ci: apply OSSF Scorecard security best practices #226

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

ci: apply OSSF Scorecard security best practices #226

wants to merge 1 commit into from

Conversation

UlisesGascon
Copy link
Member

@step-security-bot @UlisesGascon
ci: apply OSSF Scorecard security best practices
c9ff55f 
Co-authored-by: Ulises Gascón <ulisesgascongonzalez@gmail.com>
@UlisesGascon UlisesGascon requested a review from blakeembrey May 18, 2025 16:51
@UlisesGascon UlisesGascon self-assigned this May 18, 2025
@codecov Codecov
Copy link
codecov bot commented May 18, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4898ba2) to head (c9ff55f).
Report is 4 commits behind head on master.

Additional details and impacted files 
@@            Coverage Diff            @@
##            master      #226   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines          160       159    -1     
  Branches        69        69           
=========================================
- Hits           160       159    -1

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@UlisesGascon UlisesGascon mentioned this pull request May 18, 2025
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bjohansebas bjohansebas bjohansebas approved these changes

@blakeembrey blakeembrey Awaiting requested review from blakeembrey

Assignees

@UlisesGascon UlisesGascon

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@UlisesGascon @bjohansebas @step-security-bot
0