Add new security plugins, SaaS sync integration, and fix lint issues - #58
Merged
Merged
Conversation
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @khulnasoft-bot, your pull request is larger than the review limit of 150000 diff characters
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 35942090 | Triggered | Generic High Entropy Secret | a9e007f | plugins/aws/lambda/lambdaEnvSecrets.spec.js | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Reviewer's GuideAdds new secret exposure and network access security checks across AWS Lambda, GCP Cloud Functions, GitHub repos, and AWS VPC peering/subnets; introduces SaaS sync support and improves various cloud API helpers and Azure/GCP public access logic while cleaning up lint/formatting across the codebase. Sequence diagram for new SaaS sync integration flowsequenceDiagram
actor User
participant CLI as CloudExploit_CLI
participant Engine
participant SaaSSync as initializeSaasSync
participant SaaS as KhulnaSoft_SaaS_API
User ->> CLI: run scan with --sync / KHULNASOFT_SAAS_SYNC
CLI ->> SaaSSync: initializeSaasSync(cloudConfig, settings, config)
SaaSSync ->> SaaSSync: resolve saasKey, saasAccountId, saasUrl
SaaSSync ->> SaaSSync: auto-detect cloud_account_identifier
SaaSSync ->> CLI: set settings.identifier & settings.integration
CLI ->> Engine: engine(cloudConfig, settings)
Engine ->> Engine: collect cloud metadata (api_calls)
loop for each service metadata event
Engine ->> CLI: emit localEvent
CLI ->> SaaS: integration(localEvent)
SaaS ->> SaaS: POST /sync with X-Khulnasoft-Saas-Key
SaaS -->> CLI: 2xx/4xx response
end
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
khulnasoft-bot
enabled auto-merge (squash)
August 10, 2026 20:33
FortiShield
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds multiple new security checks (AWS, Azure, GCP, GitHub), SaaS sync integration, and resolves lint errors across the codebase.
Summary by Sourcery
Introduce SaaS sync integration and new security checks across AWS, Azure, GCP, and GitHub, while tightening public access and secret handling policies and improving robustness of rate/quota handling and tooling.
New Features:
Bug Fixes:
Enhancements:
Tests: