Skip to content

feat(core): add asyncapi-operation-security-defined lint rule#2759

Open
harshit078 wants to merge 72 commits into
Redocly:mainfrom
harshit078:add-asyncapi-rule
Open

feat(core): add asyncapi-operation-security-defined lint rule#2759
harshit078 wants to merge 72 commits into
Redocly:mainfrom
harshit078:add-asyncapi-rule

Conversation

@harshit078
Copy link
Copy Markdown
Contributor

@harshit078 harshit078 commented Apr 21, 2026

What/Why/How?

  • Added asyncapi-operation-security-defined rule for AsyncAPI 2.x which reports when a security scheme referenced from an operation or server security array is not defined in ``components.securitySchemes.

Reference

#2667

Testing

Screenshots (optional)

Check yourself

  • This PR follows the contributing guide
  • All new/updated code is covered by tests
  • Core code changed? - Tested with other Redocly products (internal contributions only)
  • New package installed? - Tested in different environments (browser/node)
  • Documentation update has been considered

Security

  • The security impact of the change has been considered
  • Code follows company security practices and guidelines

Note

Medium Risk
New recommended-rule errors can break existing CI for AsyncAPI, and the rule enforces security documentation correctness (not runtime auth), with nuanced server/channel/trait behavior that users must align with.

Overview
Adds the security-defined built-in lint rule for AsyncAPI 2.x and 3.x, mirroring the OpenAPI rule: it validates security scheme references on operations and servers, and requires operations to declare security when applicable servers do not cover it.

AsyncAPI 2.x checks named schemes in security requirements against components.securitySchemes, tracks root server security (ignoring components.servers), and considers channel server bindings and operation traits via new isOperationSecured helper and expanded Async2 visitor hooks.

AsyncAPI 3.x validates $ref targets under #/components/securitySchemes/, enforces operation security on root operations (not reusable components.operations), and applies channel/server applicability similar to 2.x.

The rule is wired into async2Rules / async3Rules presets (error in recommended / all, warn in minimal, off in spec). Docs, changeset, and sidebar are updated. AsyncAPI typings are tightened to support the walkers; CLI split code gets a small AnyAsyncApiComponents typing refactor only.

Breaking: AsyncAPI specs using recommended may newly fail lint until security references and missing operation security are fixed.

Reviewed by Cursor Bugbot for commit 75389dc. Bugbot is set up for automated code reviews on this repo. Configure here.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 21, 2026

🦋 Changeset detected

Latest commit: 75389dc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
Name Type
@redocly/openapi-core Minor
@redocly/cli Minor
@redocly/respect-core Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@harshit078 harshit078 changed the title feat: Add asyncapi-operation-security-defined lint rule feat(core): Add asyncapi-operation-security-defined lint rule Apr 24, 2026
@harshit078 harshit078 marked this pull request as ready for review April 24, 2026 07:51
@harshit078 harshit078 requested review from a team as code owners April 24, 2026 07:51
@harshit078 harshit078 changed the title feat(core): Add asyncapi-operation-security-defined lint rule feat(core): add asyncapi-operation-security-defined lint rule Apr 24, 2026
Copy link
Copy Markdown
Contributor

@vadyvas vadyvas left a comment

Choose a reason for hiding this comment

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

I would suggest a slightly different approach:

  1. keep the AsyncAPI logic separate and do not reuse shared logic from the OAS rule
  2. use the same rule name, security-defined, for AsyncAPI as well, and register the AsyncAPI implementation in the AsyncAPI ruleset
  3. do not update the v1 docs in this PR

I think this would make the change smaller, clearer, and safer.

Thank you for the contribution, overall the PR looks good

Comment thread packages/core/src/rules/async2/asyncapi-operation-security-defined.ts Outdated
Comment thread packages/core/src/rules/common/security-scheme-references.ts Outdated
Comment thread packages/core/src/rules/async2/index.ts Outdated
Comment thread docs/@v1/guides/lint-asyncapi.md Outdated
Comment thread packages/core/src/config/__tests__/__snapshots__/config-resolvers.test.ts.snap Outdated
@harshit078 harshit078 requested a review from vadyvas April 30, 2026 12:45
Copy link
Copy Markdown
Contributor

@vadyvas vadyvas left a comment

Choose a reason for hiding this comment

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

left a few comments, could you take a look?

'info-contact': InfoContact as Async2Rule,
'info-license-strict': InfoLicenseStrict as Async2Rule,
'operation-operationId': OperationOperationId as Async2Rule,
'security-defined': SecurityDefined,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please add support for AsyncAPI 3 as well. Right now the rule only applies to AsyncAPI2

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

okay sure !

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The code uses the rule name security-defined, but the docs still say asyncapi-operation-security-defined
Can you update related changes?

@@ -0,0 +1,83 @@
# asyncapi-operation-security-defined
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please don’t add this rule to the v1 docs

Comment thread docs/@v1/v1.sidebars.yaml Outdated
Comment thread packages/core/src/rules/async2/index.ts
Comment thread packages/core/src/utils/is-operation-secured.ts
Comment thread packages/core/src/rules/async2/security-defined.ts
Comment thread packages/core/src/rules/async3/security-defined.ts Outdated
Comment thread packages/core/src/rules/async3/security-defined.ts
Comment thread packages/core/src/rules/async3/security-defined.ts Outdated
Comment thread packages/core/src/rules/async2/security-defined.ts
Comment thread packages/core/src/rules/async2/security-defined.ts
@harshit078
Copy link
Copy Markdown
Contributor Author

Hi @AlbinaBlazhko17 , I have addressed all the refactoring you mentioned and fixed all comments by cursor. Can you check again ? Thanks for the patience to go back and forth !

Comment thread .changeset/stupid-dryers-add.md Outdated
---

Added `security-defined` rule for AsyncAPI 2.x and 3.x.
This rule reports when a security scheme referenced from an operation or server `security` array is not defined in `components.securitySchemes`.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please, add warning here, because it is breaking change due to adding new rule in recommended ruleset with error severity.
e.g.
**Warning**: this change may break workflows that relied on root-level server inheritance.
And, i think, we need to remove second sentence, which explain how rule works.

Comment thread packages/cli/src/commands/split/asyncapi/gather-asyncapi-component-files.ts Outdated
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit cc37359. Configure here.

Comment thread packages/core/src/rules/async3/security-defined.ts Outdated
Comment thread .changeset/stupid-dryers-add.md Outdated

Added `security-defined` rule for AsyncAPI 2.x and 3.x.

**Warning**: this change may break workflows that relied on root-level server inheritance.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I provided to you just an example from another PR. Please update this warning to align with this PR.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I just realiased that and completely missed that in hurry. Aplogies !

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

No worries! Please, fix the issue from bugbot and i will review PR one more time. Thanks!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Addressed cursor bot comment. The Pr is good to review again. Thanks !

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.

4 participants