feat(scan): add --platform flag for self-hosted SCM link generation

[devin-ai-integration]

Summary

The infisical scan command logs "Unknown SCM platform. Use --platform to include links in findings." when it cannot auto-detect the SCM platform from the remote hostname (e.g. self-hosted GitLab at gitlab.uhlhost.net), but the --platform flag was never actually registered on the command — resulting in Error: unknown flag: --platform when users follow the suggestion.

This PR adds the missing --platform flag to scanCmd:

// packages/cmd/scan.go init()
scanCmd.Flags().String("platform", "", "SCM platform to use for generating finding links (github, gitlab, azuredevops, bitbucket)")

// In the Run function, before calling detect.NewRemoteInfo:
platformStr, _ := cmd.Flags().GetString("platform")
if platformStr != \"\" {
    scmPlatform, err = scm.PlatformFromString(platformStr)
    // ...
}

Accepted values: github, gitlab, azuredevops, bitbucket. When specified, the platform is passed to detect.NewRemoteInfo instead of always using scm.UnknownPlatform, enabling link generation for findings on self-hosted instances.

Link to Devin session: https://app.devin.ai/sessions/38383a02822246a391f66366f48f27e0
Requested by: @0xArshdeep

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[greptile-apps]

Greptile Summary

This PR registers the missing --platform flag on scanCmd so users can explicitly specify an SCM platform (e.g. gitlab) for self-hosted instances that fail auto-detection, fixing the Error: unknown flag: --platform that users received when following the suggestion in the existing log message.

• Adds scanCmd.Flags().String("platform", ...) in init() and reads it in the Run function before calling detect.NewRemoteInfo, skipping auto-detection when a platform is provided.
• scm.PlatformFromString validates the input and calls log.Fatal on invalid values, consistent with the rest of the command's error-handling pattern.

Confidence Score: 5/5

The change is a small, focused addition of a missing flag that directly resolves a user-facing error; no existing behaviour is altered.

The new flag is correctly registered with Flags(), read with the same error-ignoring pattern used elsewhere in the file, validated through PlatformFromString, and fatal-logged on bad input before reaching detect.NewRemoteInfo. The only gap is a cosmetic omission in the flag's help string.

No files require special attention.

Important Files Changed

Filename	Overview
packages/cmd/scan.go	Adds --platform flag to scanCmd, reads it before calling detect.NewRemoteInfo, and converts the string to a scm.Platform enum via PlatformFromString; logic is correct and error-handling follows existing file patterns.

_{Reviews (1): Last reviewed commit: "feat(scan): add --platform flag for self..." | Re-trigger Greptile}

[adilsitos]

it seems to be disabled on purpose.

[devin-ai-integration]

This code is forked from gitleaks which does have the --platform flag registered. When the scan code was ported to the Infisical CLI, the flag registration was left out but the log message referencing it ("Unknown SCM platform. Use --platform to include links in findings." in detect/git.go:149) was kept — which is what's causing the customer confusion.

If it was intentionally disabled, should we update the log message to remove the --platform reference instead? Happy to go either direction — but as-is, it's telling users to use a flag that doesn't exist.