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.

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

Manually resolve send and cookie dependencies to safe versions #16319

Merged
merged 3 commits into from
Oct 22, 2024
Merged

Manually resolve send and cookie dependencies to safe versions #16319

merged 3 commits into from
Oct 22, 2024

Conversation

jpandersen87
Copy link
Collaborator

Fixes #16317

This PR manually resolves dependencies to safe versions temporarily until their parent dependencies do so.

@jpandersen87 jpandersen87 self-assigned this Oct 22, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Oct 22, 2024 •
edited
Loading

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
npm/cookie 1.0.1 🟢 6.9
Details
CheckScoreReason
Code-Review⚠️ 2Found 7/30 approved changesets -- score normalized to 2
Maintained🟢 1030 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
License🟢 10license file detected
Binary-Artifacts🟢 10no binaries found in the repo
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Pinned-Dependencies🟢 4dependency not pinned by hash detected -- score normalized to 4
Packaging⚠️ -1packaging workflow not detected
Token-Permissions🟢 9detected GitHub workflow tokens with excessive permissions
Security-Policy🟢 10security policy file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
Fuzzing⚠️ 0project is not fuzzed
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
Vulnerabilities🟢 100 existing vulnerabilities detected
npm/send 1.1.0 🟢 5.1
Details
CheckScoreReason
Binary-Artifacts🟢 10no binaries found in the repo
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
CI-Tests🟢 79 out of 12 merged PRs checked by a CI test -- score normalized to 7
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Code-Review🟢 5found 7 unreviewed changesets out of 15 -- score normalized to 5
Contributors🟢 1029 different organizations found -- score normalized to 10
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Dependency-Update-Tool⚠️ 0no update tool detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Maintained🟢 77 commit(s) out of 30 and 2 issue activity out of 30 found in the last 90 days -- score normalized to 7
Packaging⚠️ -1no published package detected
Pinned-Dependencies🟢 3dependency not pinned by hash detected -- score normalized to 3
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
Security-Policy🟢 10security policy file detected
Signed-Releases⚠️ -1no releases found
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Vulnerabilities🟢 10no vulnerabilities detected

Scanned Manifest Files

frontend-react/yarn.lock

@jpandersen87 jpandersen87 enabled auto-merge (squash) October 22, 2024 20:40
@github-actions GitHub Actions
Copy link
Contributor

Branch deployed to Chromatic 🚀.

  • ⚠️ Detected 3 tests with visual changes.
  • ✅ All tests passed.

View via:

@sonarqubecloud SonarQubeCloud
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

@jpandersen87 jpandersen87 merged commit 0522693 into master Oct 22, 2024
29 of 31 checks passed
@jpandersen87 jpandersen87 deleted the experience/16317-Manually-resolve-send-and-cookie-dependencies-to-safe-versions branch October 22, 2024 21:28
@github-actions GitHub Actions
Copy link
Contributor

⚠️ Broken Links ⚠️

❌ https://www.cdc.gov/od/foia

Error: Request failed with status code 403

❌ https://www.hhs.gov/vulnerability-disclosure-policy/index.html

Error: Request failed with status code 403

❌ https://www.hl7.org/implement/standards/product_brief.cfm?product_id=185

Error: Request failed with status code 403

❌ https://www.cdc.gov/poxvirus/mpox/lab-personnel/report-results.html

Error: Request failed with status code 404

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@victor-chaparro victor-chaparro victor-chaparro approved these changes

@etanb etanb Awaiting requested review from etanb

Assignees

@jpandersen87 jpandersen87

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Manually resolve send and cookie dependencies to safe versions
2 participants
@jpandersen87 @victor-chaparro