Skip to content

issue 2: file hash cache as mentioned in the README about semgrep, the scan is currently slow #2

@Prateek219

Description

@Prateek219

The existing cache only tracks filenames, meaning it might re-scan large files even if the content (and the potential secrets within) hasn't changed.we can use md5sum to scan files which are changed are you open to PR.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions