OIDC Client implementation (conformance)

[dvoytenko]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
example-marketplace-integration	Ready	Preview	Comment	Oct 9, 2025 11:35pm

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​react-dom@​18.3.7 ⏵ 18.2.24
	autoprefixer@​10.4.21 ⏵ 10.4.19
	@​types/​react@​18.3.23 ⏵ 18.2.74
	@​types/​lodash@​4.17.17 ⏵ 4.17.0
	nanoid@​5.1.5 ⏵ 5.0.7		-3
	@​types/​node@​20.17.52 ⏵ 20.12.4
	postcss@​8.5.4 ⏵ 8.4.38
	react@​18.3.1 ⏵ 18.2.0
	tailwindcss@​3.4.17 ⏵ 3.4.3
	jose@​5.10.0 ⏵ 5.2.4
	prettier@​3.5.3 ⏵ 3.6.2	+1
	typescript@​5.8.3 ⏵ 5.4.3	+1		+1
	react-dom@​18.3.1 ⏵ 18.2.0
	openid-client@​6.6.2
	eslint@​8.57.1 ⏵ 8.57.0	+1
	zod@​3.25.39 ⏵ 3.25.50	+1			+2

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		[email protected] has a High CVE. CVE: GHSA-grv7-fg5c-xmjg Uncontrolled resource consumption in braces (HIGH) Affected versions: < 3.0.3 Patched version: 3.0.3 From: pnpm-lock.yaml → npm/[email protected] → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a CVE? 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 [email protected]. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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