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
Copy file name to clipboardExpand all lines: README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -556,7 +556,7 @@ By default, govulncheck makes requests to the Go vulnerability database at https
556
556
557
557
-[safesql](https://github.com/stripe/safesql):warning: — Static analysis tool for Golang that protects against SQL injections.
558
558
559
-
-[shisho](https://docs.shisho.dev/) — A lightweight static code analyzer designed for developers and security teams. It allows you to analyze and transform source code with an intuitive DSL similar to sed, but for code.
559
+
-[shisho](https://docs.shisho.dev/):warning:— A lightweight static code analyzer designed for developers and security teams. It allows you to analyze and transform source code with an intuitive DSL similar to sed, but for code.
560
560
561
561
-[staticcheck](https://staticcheck.io) — Go static analysis that specialises in finding bugs, simplifying code and improving performance.
562
562
@@ -1117,6 +1117,8 @@ YAPF follows a distinctive methodology, originating from the 'clang-format' tool
1117
1117
1118
1118
-[cargo-inspect](https://github.com/mre/cargo-inspect):warning: — Inspect Rust code without syntactic sugar to see what the compiler does behind the curtains.
1119
1119
1120
+
-[cargo-semver-checks](https://crates.io/crates/cargo-semver-checks) — Scan your Rust crate releases for semver violations. It can be used either directly via the CLI, as a GitHub Action in CI, or via release managers like `release-plz`. It found semver violations in [more than 1 in 6 of the top 1000 most-downloaded crates](https://predr.ag/blog/semver-violations-are-common-better-tooling-is-the-answer/) on crates.io.
1121
+
1120
1122
-[cargo-show-asm](https://github.com/pacak/cargo-show-asm) — cargo subcommand showing the assembly, LLVM-IR and MIR generated for Rust code
1121
1123
1122
1124
-[cargo-spellcheck](https://github.com/drahnr/cargo-spellcheck) — Checks all your documentation for spelling and grammar mistakes with hunspell (ready) and languagetool (preview)
@@ -2171,7 +2173,7 @@ TruffleHog is an open source secret-scanning engine that resolves exposed secret
2171
2173
2172
2174
-[kics](https://kics.io/) — Find security vulnerabilities, compliance issues, and infrastructure misconfigurations in your infrastructure-as-code. Supports Terraform, Kubernetes, Docker, AWS CloudFormation and Ansible
2173
2175
2174
-
-[shisho](https://docs.shisho.dev/) — A lightweight static code analyzer designed for developers and security teams. It allows you to analyze and transform source code with an intuitive DSL similar to sed, but for code.
2176
+
-[shisho](https://docs.shisho.dev/):warning:— A lightweight static code analyzer designed for developers and security teams. It allows you to analyze and transform source code with an intuitive DSL similar to sed, but for code.
"description": "Scan your Rust crate releases for semver violations. It can be used either directly via the CLI, as a GitHub Action in CI, or via release managers like `release-plz`. It found semver violations in [more than 1 in 6 of the top 1000 most-downloaded crates](https://predr.ag/blog/semver-violations-are-common-better-tooling-is-the-answer/) on crates.io.",
1882
+
"discussion": null,
1883
+
"deprecated": null,
1884
+
"resources": null,
1885
+
"reviews": null,
1886
+
"demos": null,
1887
+
"wrapper": null
1888
+
},
1862
1889
"cargo-show-asm": {
1863
1890
"name": "cargo-show-asm",
1864
1891
"categories": [
@@ -16759,7 +16786,7 @@
16759
16786
"plans": null,
16760
16787
"description": "A lightweight static code analyzer designed for developers and security teams. It allows you to analyze and transform source code with an intuitive DSL similar to sed, but for code.",
0 commit comments