From 37e2d845a004489242ed840b0c69777fbd8fd93f Mon Sep 17 00:00:00 2001 From: UncleSp1d3r Date: Sat, 4 Jul 2026 19:27:07 -0400 Subject: [PATCH 1/5] docs: add Code of Conduct and citation metadata Fill the one missing community-health file and polish related packaging: - Add CODE_OF_CONDUCT.md (Contributor Covenant 2.1) with enforcement contact support@evilbitlabs.io, matching the SECURITY.md convention - Reference the Code of Conduct from CONTRIBUTING.md, the README Contributing section, and the issue-template contact links - Add CITATION.cff so the tool can be cited (Apache-2.0, org author) - Add a language tag to the README TTY-table code fence (MD040) Signed-off-by: UncleSp1d3r --- .github/ISSUE_TEMPLATE/config.yml | 3 ++ CITATION.cff | 21 ++++++++ CODE_OF_CONDUCT.md | 85 +++++++++++++++++++++++++++++++ CONTRIBUTING.md | 4 ++ README.md | 4 +- 5 files changed, 115 insertions(+), 2 deletions(-) create mode 100644 CITATION.cff create mode 100644 CODE_OF_CONDUCT.md diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index fc31ac7..2d74e87 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -13,3 +13,6 @@ contact_links: - name: Known gotchas url: https://github.com/EvilBit-Labs/Stringy/blob/main/GOTCHAS.md about: Hard-won lessons and edge cases before you dig into the code. + - name: Code of Conduct + url: https://github.com/EvilBit-Labs/Stringy/blob/main/CODE_OF_CONDUCT.md + about: The standards we expect from everyone participating in this project. diff --git a/CITATION.cff b/CITATION.cff new file mode 100644 index 0000000..f26a8c4 --- /dev/null +++ b/CITATION.cff @@ -0,0 +1,21 @@ +cff-version: 1.2.0 +message: "If you use this software, please cite it using these metadata." +title: Stringy +abstract: >- + A smarter alternative to the strings command that leverages format-specific + knowledge and semantic classification to extract meaningful strings from ELF, + PE, and Mach-O binaries. +type: software +authors: + - name: "EvilBit Labs" + website: "https://evilbitlabs.io" +repository-code: "https://github.com/EvilBit-Labs/Stringy" +url: "https://evilbitlabs.io/Stringy/" +license: Apache-2.0 +version: 0.1.0 +keywords: + - binary + - strings + - analysis + - reverse-engineering + - malware diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..c35ebc9 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,85 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our community include: + +- Demonstrating empathy and kindness toward other people +- Being respectful of differing opinions, viewpoints, and experiences +- Giving and gracefully accepting constructive feedback +- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience +- Focusing on what is best not just for us as individuals, but for the overall community + +Examples of unacceptable behavior include: + +- The use of sexualized language or imagery, and sexual attention or advances of any kind +- Trolling, insulting or derogatory comments, and personal or political attacks +- Public or private harassment +- Publishing others' private information, such as a physical or email address, without their explicit permission +- Other conduct which could reasonably be considered inappropriate in a professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. + +Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [support@evilbitlabs.io](mailto:support@evilbitlabs.io). + +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series of actions. + +**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][mozilla coc]. + +For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][faq]. Translations are available at [https://www.contributor-covenant.org/translations][translations]. + +[faq]: https://www.contributor-covenant.org/faq +[homepage]: https://www.contributor-covenant.org +[mozilla coc]: https://github.com/mozilla/diversity +[translations]: https://www.contributor-covenant.org/translations +[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2a53f00..43ecc68 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -4,6 +4,10 @@ Thanks for your interest in Stringy. This guide explains how to propose changes > **Before you start:** check [GOTCHAS.md](GOTCHAS.md) for hard-won lessons and edge cases organized by domain (struct literals, CLI, CI, dependencies, pipeline). It will save you from common pitfalls that have tripped up contributors before. +## Code of Conduct + +By participating in this project you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md). Please report unacceptable behavior to [support@evilbitlabs.io](mailto:support@evilbitlabs.io). + ## Quick start 1. Search existing issues and pull requests before filing a new one. diff --git a/README.md b/README.md index 486d1f4..4469e34 100644 --- a/README.md +++ b/README.md @@ -69,7 +69,7 @@ cat target_binary | stringy - **TTY table:** -``` +```text String | Tags | Score | Section -----------------------------------------|------------|-------|-------- https://api.example.com/v1/ | url | 95 | .rdata @@ -133,7 +133,7 @@ Quick links: [Installation](docs/src/installation.md) | [Quick Start](docs/src/q ## Contributing -See [CONTRIBUTING.md] for development setup, coding guidelines, and submission process. +See [CONTRIBUTING.md] for development setup, coding guidelines, and submission process. Participation is governed by our [Code of Conduct](CODE_OF_CONDUCT.md). ## License From a53fd7544b7d4f5ee29e1b7a61e7011491b471c5 Mon Sep 17 00:00:00 2001 From: UncleSp1d3r Date: Sat, 4 Jul 2026 19:37:00 -0400 Subject: [PATCH 2/5] chore: remove unused Codex configuration for tessl Signed-off-by: UncleSp1d3r --- .codex/config.toml | 4 ---- 1 file changed, 4 deletions(-) delete mode 100644 .codex/config.toml diff --git a/.codex/config.toml b/.codex/config.toml deleted file mode 100644 index 4334324..0000000 --- a/.codex/config.toml +++ /dev/null @@ -1,4 +0,0 @@ -[mcp_servers.tessl] -type = "stdio" -command = "tessl" -args = [ "mcp", "start" ] From 21c97dbf9749bc793c9bd43d148fdaec0c96e312 Mon Sep 17 00:00:00 2001 From: UncleSp1d3r Date: Sat, 4 Jul 2026 19:44:36 -0400 Subject: [PATCH 3/5] chore: update settings and remove unused mcpServers configuration Signed-off-by: UncleSp1d3r --- .claude/settings.json | 5 +++-- .mcp.json | 10 ++-------- tessl.json | 40 ---------------------------------------- 3 files changed, 5 insertions(+), 50 deletions(-) delete mode 100644 tessl.json diff --git a/.claude/settings.json b/.claude/settings.json index 4ce405d..c789039 100644 --- a/.claude/settings.json +++ b/.claude/settings.json @@ -11,6 +11,7 @@ "comprehensive-review@claude-code-workflows": true, "superpowers@claude-plugins-official": true, "github@claude-plugins-official": true, - "ecc@everything-claude-code": true + "ecc@everything-claude-code": true, + "rust-skills@rust-skills": true } -} +} \ No newline at end of file diff --git a/.mcp.json b/.mcp.json index e3fe521..7001130 100644 --- a/.mcp.json +++ b/.mcp.json @@ -1,9 +1,3 @@ { - "mcpServers": { - "tessl": { - "type": "stdio", - "command": "tessl", - "args": ["mcp", "start"] - } - } -} + "mcpServers": {} +} \ No newline at end of file diff --git a/tessl.json b/tessl.json deleted file mode 100644 index 6102c19..0000000 --- a/tessl.json +++ /dev/null @@ -1,40 +0,0 @@ -{ - "name": "stringy", - "mode": "vendored", - "dependencies": { - "actionbook/rust-skills": { - "version": "3ea748280d2fa5680675fe4abe1a5e764f7c021e", - "source": "https://github.com/actionbook/rust-skills", - "include": { - "skills": [ - "coding-guidelines", - "domain-cli", - "m01-ownership", - "m02-resource", - "m03-mutability", - "m04-zero-cost", - "m05-type-driven", - "m06-error-handling", - "m07-concurrency", - "m09-domain", - "m10-performance", - "m11-ecosystem", - "m12-lifecycle", - "m13-domain-error", - "m14-mental-model", - "m15-anti-pattern", - "meta-cognition-parallel", - "rust-call-graph", - "rust-code-navigator", - "rust-deps-visualizer", - "rust-learner", - "rust-refactor-helper", - "rust-skill-creator", - "rust-symbol-analyzer", - "rust-trait-explorer", - "unsafe-checker" - ] - } - } - } -} From cd0f084b1f33e5a4e563fb4f48761ad440577c5a Mon Sep 17 00:00:00 2001 From: UncleSp1d3r Date: Sat, 4 Jul 2026 20:02:45 -0400 Subject: [PATCH 4/5] chore: fix formatting issues in configuration files Signed-off-by: UncleSp1d3r --- .claude/settings.json | 2 +- .mcp.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.claude/settings.json b/.claude/settings.json index c789039..8795148 100644 --- a/.claude/settings.json +++ b/.claude/settings.json @@ -14,4 +14,4 @@ "ecc@everything-claude-code": true, "rust-skills@rust-skills": true } -} \ No newline at end of file +} diff --git a/.mcp.json b/.mcp.json index 7001130..da39e4f 100644 --- a/.mcp.json +++ b/.mcp.json @@ -1,3 +1,3 @@ { "mcpServers": {} -} \ No newline at end of file +} From 038c14b464aca33d771c9e42af9ac89d36399476 Mon Sep 17 00:00:00 2001 From: UncleSp1d3r Date: Sat, 4 Jul 2026 20:27:37 -0400 Subject: [PATCH 5/5] docs: fix README jq example for JSONL output The --json formatter emits JSON Lines (one object per line), not a JSON array, so the piped example used array-iteration syntax (.[]) that errors on every line with 'Cannot index string with string'. Replace with a line-by-line filter: jq 'select(.tags | index("Url"))'. Signed-off-by: UncleSp1d3r --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4469e34..fdae4bf 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ stringy --top 50 target_binary # Output formats stringy --json target_binary stringy --yara target_binary -stringy --json target_binary | jq '.[] | select(.tags[] | contains("Url"))' +stringy --json target_binary | jq 'select(.tags | index("Url"))' # Raw extraction (no classification or ranking) stringy --raw target_binary