Skip to content

OOP for project writers #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tmikula-dev merged 10 commits into from
Jan 26, 2026

Test updates for trace logging.

4afdeb9
Select commit
Loading
Failed to load commit list.
Merged

OOP for project writers #104

Test updates for trace logging.
4afdeb9
Select commit
Loading
Failed to load commit list.
GitHub Advanced Security / AquaSec failed Jan 14, 2026 in 5s

4 new alerts including 4 high severity security vulnerabilities

New alerts in code changed by this pull request

Security Alerts:

  • 4 high

See annotations below for details.

View all branch alerts.

Annotations

Check failure on line 138 in src/writers/writer_postgres.py

See this annotation in the file changed.

Code scanning / AquaSec

sqlalchemy safe query execution High

Merging user inputs directly into SQL queries without precautions can lead to SQL Injection vulnerabilities. It is highly recomended to use prepared statements to ensure data is handled securely, with SQLAlchemy's TextualSQL being an ideal tool for this. It supports named parameters for safer query construction. For more complex queries, SQLAlchemy's SQL Expression Language or Schema Definition Language are recommended. Opting for SQLAlchemy ORM is often the safest and most efficient route for database operations.

Check failure on line 185 in src/writers/writer_postgres.py

See this annotation in the file changed.

Code scanning / AquaSec

sqlalchemy safe query execution High

Merging user inputs directly into SQL queries without precautions can lead to SQL Injection vulnerabilities. It is highly recomended to use prepared statements to ensure data is handled securely, with SQLAlchemy's TextualSQL being an ideal tool for this. It supports named parameters for safer query construction. For more complex queries, SQLAlchemy's SQL Expression Language or Schema Definition Language are recommended. Opting for SQLAlchemy ORM is often the safest and most efficient route for database operations.

Check failure on line 222 in src/writers/writer_postgres.py

See this annotation in the file changed.

Code scanning / AquaSec

sqlalchemy safe query execution High

Merging user inputs directly into SQL queries without precautions can lead to SQL Injection vulnerabilities. It is highly recomended to use prepared statements to ensure data is handled securely, with SQLAlchemy's TextualSQL being an ideal tool for this. It supports named parameters for safer query construction. For more complex queries, SQLAlchemy's SQL Expression Language or Schema Definition Language are recommended. Opting for SQLAlchemy ORM is often the safest and most efficient route for database operations.

Check failure on line 262 in src/writers/writer_postgres.py

See this annotation in the file changed.

Code scanning / AquaSec

sqlalchemy safe query execution High

Merging user inputs directly into SQL queries without precautions can lead to SQL Injection vulnerabilities. It is highly recomended to use prepared statements to ensure data is handled securely, with SQLAlchemy's TextualSQL being an ideal tool for this. It supports named parameters for safer query construction. For more complex queries, SQLAlchemy's SQL Expression Language or Schema Definition Language are recommended. Opting for SQLAlchemy ORM is often the safest and most efficient route for database operations.