Skip to content

Conversation

@jdalton
Copy link
Contributor

@jdalton jdalton commented Jan 7, 2026

Summary

Fixes CI pipeline failures and resolves 2 high-severity Dependabot security alerts.

Changes

CI Fix:

  • Remove unused silence parameter from getDefaultOrgSlug() call in cmd-fix.mts
  • Completes the parameter removal started in commit 2b6d61a

Security Updates:

Test Plan

  • ✅ TypeScript type checks pass
  • ✅ ESLint checks pass
  • ✅ All unit tests pass
  • ✅ Pre-commit hooks pass

Note

Resolves CI/type-check issues and addresses dependency updates.

  • Updates packages/cli/src/commands/fix/cmd-fix.mts to call getDefaultOrgSlug() without the silence parameter
  • Bumps dependencies: glob13.0.0 and qs6.14.1 via package.json overrides and pnpm-lock.yaml (removing older transitive variants)

Written by Cursor Bugbot for commit 11ce67d. Configure here.

@socket-security-staging
Copy link

socket-security-staging bot commented Jan 7, 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
License policy violation: npm glob under BlueOak-1.0.0

License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (npm metadata)

License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/LICENSE.md)

License: BlueOak-1.0.0 - the applicable license policy does not allow this license (4) (package/package.json)

From: pnpm-lock.yamlnpm/@npmcli/[email protected]npm/@npmcli/[email protected]npm/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity-Staging ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity-Staging 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

@jdalton jdalton closed this Jan 8, 2026
@jdalton jdalton force-pushed the jdalton/fix-ci-lint-type-checks branch from 9bd24bd to 2b6d61a Compare January 8, 2026 18:17
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