You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixed [#8809](https://github.com/biomejs/biome/issues/8809), [#7985](https://github.com/biomejs/biome/issues/7985), and [#8136](https://github.com/biomejs/biome/issues/8136): the `noSecrets` rule no longer reports false positives on common CamelCase identifiers like `paddingBottom`, `backgroundColor`, `unhandledRejection`, `uncaughtException`, and `IngestGatewayLogGroup`.
6
+
7
+
The entropy calculation algorithm now uses "average run length" to distinguish between legitimate CamelCase patterns (which have longer runs of same-case letters) and suspicious alternating case patterns (which have short runs).
- Original paper for Shannon Entropy: https://ieeexplore.ieee.org/abstract/document/6773024/
432
+
- Fix for false positives on CamelCase: https://github.com/biomejs/biome/issues/8809
1.Removethesecretfromyourcode. Ifyou've already committed it, consider removing the commit entirely from your git tree.
441
+
2.Ifneeded, use environment variables or a secure secret management system to store sensitive data.
442
+
3. If this is a false positive, consider adding an inline disable comment, or tweak the entropy threshold. See options in our docs.
443
+
This rule only catches basic vulnerabilities. For more robust, proper solutions, check out our recommendations at: https://biomejs.dev/linter/rules/no-secrets/#recommendations
0 commit comments