Summary

How about to support Makfile variable patter $(VAR) in database-connection-string rule?
This must improve compatibility with Make-based projects.

Basic example

My Makefile includes DB connection information like this:

DB_URL = postgres://$(PGUSER):$(PGPASSWORD)@$(PGHOST)/$(PGDATABASE)

This Makefile is warned by secretlint. It seems such variable string like $(PGPASSWORD) is not included in isVariableLikeString function.

I'm glad if this is allowed as another variables pattern.
Here's example.

function isVariableLikeString(str: string): boolean {
    const variablePatterns = [
        /\$\{[^}]{1,50}\}/, // ${var}
        /\{\{[^}]{1,50}\}\}/, // {{var}}
        /\{[^}]{1,50}\}/, // {var}
        /%[A-Z_]{1,30}%/, // %VAR%
        /\$[A-Z_]{1,30}/, // $VAR
        /\$\([^)]{1,50}\)/, // $(var) - *** Add line like this? ***
    ];

    return variablePatterns.some((pattern) => pattern.test(str));
}

Motivation

• I think it is common to have database connection strings in a Makefile.
• Supporting common variable patterns would make secretlint even more useful.
• Of course, it helps my project, I would be happy, too.