refactor: Security upgrade parse from 6.1.1 to 7.0.1

[parseplatformorg]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-PARSE-13053302	790
	Prototype Pollution SNYK-JS-PARSE-13551630	700

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• 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 fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution

Summary by CodeRabbit

• Chores
  • Updated parse library dependency to the latest version.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[coderabbitai]

📝 Walkthrough

Walkthrough

The parse dependency in package.json is updated from version 6.1.1 to 7.0.1, a major version bump. No other code changes or functional modifications are present in this pull request.

Changes

Cohort / File(s)	Summary
Dependency version update package.json	Update parse dependency from 6.1.1 to 7.0.1 (major version bump)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description does not follow the repository’s required template, as it omits the checklist, issue reference, “Approach” section, and “TODOs before merging” items defined in the template, instead using a generic Snyk-generated format. This means key information and structure required by the project guidelines are missing.	Please update the description to use the repository’s template by adding the checklist validation boxes, linking the related issue, describing the approach taken, and listing any required TODOs before merging such as tests, changelog entries, and documentation updates.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title clearly and concisely reflects the primary change by specifying a security‐focused dependency upgrade of the “parse” package from version 6.1.1 to 7.0.1, which aligns with the actual modifications in the pull request. It succinctly communicates the purpose and scope of the update without unnecessary detail or ambiguity.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-709f6dc4eed3f18e8006af8fb0cafd59

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4b83f17 and 24058ae.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (1)

package.json (1)

31-31: parse 7.0.1 upgrade validated—all tests pass with full coverage

Ran full test suite: 93 specs executed successfully with 100% coverage (Statements, Branches, Functions, Lines). No regressions detected. The major version bump is compatible with the codebase.

Note: npm flagged a Node engine version mismatch ([email protected] requires Node 18, 19, 20, or 22, but tests ran on Node v24.3.0). Tests passed despite this, but verify Node version compatibility in your CI/deployment environment matches the declared constraints.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[parseplatformorg]

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

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (69840c6) to head (24058ae).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #455   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines         1172      1172           
=========================================
  Hits          1172      1172           

☔ 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.