Skip to content

Conversation

@skyeyeye
Copy link

No description provided.

@socket-security
Copy link

socket-security bot commented Jan 21, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​types/​node@​22.19.3 ⏵ 22.19.7100 +110081 +196 +1100
Addedexpress@​5.2.19810010091100
Updated@​biomejs/​biome@​1.9.4 ⏵ 2.3.11100 +710010097100

View full report

Copy link
Member

@bjohansebas bjohansebas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate of #111 , but please use the latest version of Biome.

Copy link
Author

@skyeyeye skyeyeye left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

chore: upgrade biome to ^2.3.11
This PR upgrades Biome to ^2.3.11 and runs the official migration to update the configuration.

Changes:

  • Upgrade @biomejs/biome to ^2.3.11
  • Run biome migrate --write to update config
  • Update package-lock.json for reproducible installs

@skyeyeye skyeyeye changed the title biome-version2 update chore: upgrade Biome to v2.3.11 Closes #111 Jan 22, 2026
@socket-security
Copy link

socket-security bot commented Jan 22, 2026

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm safer-buffer is 94.0% likely obfuscated

Confidence: 0.94

Location: Package overview

From: package-lock.jsonnpm/express@5.2.1npm/safer-buffer@2.1.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Signed-off-by: Ayush Saha <ayushsaha.work@gmail.com>
Comment on lines +35 to +37
"dependencies": {
"express": "^5.2.1"
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don’t need Express as a dependency or a devDependency, remove it.

Suggested change
"dependencies": {
"express": "^5.2.1"
}

Comment on lines +6 to +10
const reqBody = req.body;
const reqQuery = req.query;
const reqQueryTest = req.query.test;
const reqOther = req.params.other;
const reqOtherNested = req.params.other.nested;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why?

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.

2 participants