Skip to content

fix: Incorrect Security Stats when using --enableAutoCsp #58

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
merged 1 commit into from
Sep 26, 2025
Merged

fix: Incorrect Security Stats when using --enableAutoCsp #58

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions runner/ratings/stats.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,10 +86,23 @@ export function calculateBuildAndCheckStats(
}
}
securityStats ??= { appsWithErrors: 0, appsWithoutErrors: 0 };
const numCspViolations = (result.build.cspViolations || []).length;
const { numCspViolations, numTrustedTypesViolations } = (
result.build.cspViolations || []
).reduce(
(acc, v) => {
if (v['blocked-uri'] === 'trusted-types-sink') {
acc.numTrustedTypesViolations++;
} else {
acc.numCspViolations++;
}
return acc;
},
{ numCspViolations: 0, numTrustedTypesViolations: 0 }
);

const hasSafetyViolations =
(result.build.safetyWebReportJson?.[0]?.violations?.length ?? 0) > 0;

// TODO: Consider numTrustedTypesViolations once we update autoCsp and re-enable the rating.
if (hasSafetyViolations || numCspViolations > 0) {
securityStats.appsWithErrors++;
} else {
Expand Down
Loading