Skip to content

[Snyk] Upgrade write-file-atomic from 7.0.1 to 8.0.0 - #93

Closed
Aravind-Kumar-cstk wants to merge 1 commit into
masterfrom
snyk-upgrade-727c56070bcbfe38d745634818f92930
Closed

[Snyk] Upgrade write-file-atomic from 7.0.1 to 8.0.0#93
Aravind-Kumar-cstk wants to merge 1 commit into
masterfrom
snyk-upgrade-727c56070bcbfe38d745634818f92930

Conversation

@Aravind-Kumar-cstk

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to upgrade write-file-atomic from 7.0.1 to 8.0.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released 21 days ago.

Release notes
Package name: write-file-atomic from write-file-atomic GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade write-file-atomic from 7.0.1 to 8.0.0.

See this package in npm:
write-file-atomic

See this project in Snyk:
[snyk-project-url-redacted]
@Aravind-Kumar-cstk
Aravind-Kumar-cstk requested a review from a team as a code owner May 30, 2026 04:27
@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

✅ BUILD PASSED - All security checks passed

@cs-raj
cs-raj force-pushed the snyk-upgrade-727c56070bcbfe38d745634818f92930 branch from 49997ab to 8a398af Compare August 7, 2026 11:40
@snyk-io

snyk-io Bot commented Aug 7, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@cs-raj

cs-raj commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Closing this stale automated dependency update PR as part of repository branch cleanup. If these dependencies still need updating, a fresh Snyk/Dependabot scan will create new PRs.

@cs-raj cs-raj closed this Aug 14, 2026
@cs-raj
cs-raj deleted the snyk-upgrade-727c56070bcbfe38d745634818f92930 branch August 14, 2026 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants