[GCP] Scans not functioning due to incorrect field name in credential file documentation

[keshavga1209]

GCP credential docs

For using the GCP using credential file, it suggests the following format:

{
    "project": "",
    "client_email": "",
    "private_key": ""
}

But, as per this index.js line, one is expected to provide "project_id" and not "project"

Consequences: This mismatch is causing the "project" field provided to be ignored, hence effectively scans are not happening on the project even though it appears it's being scanned, since no error is raised. This can cause false negatives.

Suggestion: Add input validation to surface an explicit error when the required field is missing and rectify the documentation.

If this sounds correct, please assign this issue to me and I can raise the fix.

[hiSandog]

This seems like both a docs bug and a validation opportunity. The README should use the field name the scanner actually expects, but the scanner could also detect the common documented shape and return a targeted error such as project_id is required; README previously showed project. That would help users who already copied the old credential template and otherwise just see GCP scans fail.