mrbrightsides/stc-swc

STC for SWC addresses a useful data-integration problem by converting Mythril and Slither security reports into a shared analytics format. The repository separates scanner-specific extraction, schema normalization, SWC metadata enrichment, and CSV or NDJSON export into distinct modules. Providing both a command-line path and a Streamlit interface makes the converter accessible to automation pipelines and interactive users. The README clearly explains the intended STC ecosystem, output columns, example records, and future analyzer support. A DOI, live application link, sample output directory, and MIT license also help establish the project’s purpose and availability.
Several implementation issues currently make the stable label difficult to support. The documented python -m stc_swc.cli command cannot work because cli.py is located at the repository root rather than inside the package. There is no packaging configuration or automated test suite, and the only workflow keeps the hosted app awake instead of validating parsers and output schemas. More seriously, the Streamlit application calls st.set_page_config twice, which Streamlit rejects, and it repeats imports, commit-hash helpers, metadata loops, and SWC mappings. It also writes uploaded reports and generated files into shared fixed directories, which can cause collisions or expose one session’s results to another in a multi-user deployment. Moving the CLI into the package, adding pyproject.toml, using per-session temporary storage, and testing real Mythril and Slither fixtures would provide the highest value. Input-size limits, JSON schema validation, structured error handling, and pinned dependency ranges would further improve reliability and safety.