Files

T

Dave Hubbard ee476c7e56 update huggingface to fix unbounded resources bug (#5204 )

When a model's owner (user/org) isn't in the token's fine-grained scopes
AND the model itself isn't directly scoped, the Permission can end up
blank, which is a proto violation.  So, move those cases to unbounded
resources.

2026-08-13 13:42:15 -04:00

analyzers

update huggingface to fix unbounded resources bug (#5204 )

2026-08-13 13:42:15 -04:00

config

[analyze] Implement Analyzer interface for github (#3110 )

2024-07-26 14:47:03 -07:00

generate_permissions

Enable errcheck and staticcheck for golangci-lint v2 and resolve all issues (#4924 )

2026-05-15 17:07:14 +05:00

cli.go

[INS-241] Datadogapikey detector (#4627 )

2026-03-11 16:04:51 +05:00

README.md

Support for kebab case and dot notation in permission generation tool (#3222 )

2024-08-15 10:07:42 -07:00

README.md

Implementing Analyzers

Defining the Permissions

Permissions can be defined in:

lower snake case as permission_name:access_level
kebab case as permission-name:read
dot notation as permission.name:read

The Permissions are initially defined as a yaml file.

At the top of the analyzer implementation you specify the go generate command.

You can install the generator with go install github.com/trufflesecurity/trufflehog/v3/pkg/analyzer/generate_permissions.

Then you can run go generate ./... to generate the Permission types for the analyzer.

The generated Permission types are to be used in the AnalyzerResult struct when defining the Permissions and in your code.