Skip to content

Update dotnet.yml

Update dotnet.yml #15

Triggered via push April 10, 2025 10:33
Status Success
Total duration 32s
Artifacts

dotnet.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
build: src/EntityGuardian/Storages/SqlServer/SqlServerStorage.cs#L16
Method 'ExecuteSqlRaw' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSql' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
build: src/EntityGuardian/Storages/SqlServer/SqlServerStorage.cs#L15
Method 'ExecuteSqlRaw' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSql' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
build: src/EntityGuardian/Storages/SqlServer/SqlServerStorage.cs#L16
Method 'ExecuteSqlRaw' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSql' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
build: src/EntityGuardian/Storages/SqlServer/SqlServerStorage.cs#L15
Method 'ExecuteSqlRaw' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSql' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
build: src/EntityGuardian/Storages/SqlServer/SqlServerStorage.cs#L16
Method 'ExecuteSqlRaw' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSql' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
build: src/EntityGuardian/Storages/SqlServer/SqlServerStorage.cs#L15
Method 'ExecuteSqlRaw' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSql' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.