Skip to content

Leaderboard: konflux-ci/konflux-ui (82.6/100 - Gold)#482

Draft
StanislavJochman wants to merge 1 commit into
ambient-code:mainfrom
StanislavJochman:leaderboard-konflux-ci-konflux-ui-2026-05-28T20-22-45
Draft

Leaderboard: konflux-ci/konflux-ui (82.6/100 - Gold)#482
StanislavJochman wants to merge 1 commit into
ambient-code:mainfrom
StanislavJochman:leaderboard-konflux-ci-konflux-ui-2026-05-28T20-22-45

Conversation

@StanislavJochman
Copy link
Copy Markdown

@StanislavJochman StanislavJochman commented May 28, 2026

Leaderboard Submission

Repository: konflux-ci/konflux-ui
Host: GitHub
Score: 82.6/100
Tier: Gold
Submitted by: @StanislavJochman

Validation Checklist

  • Repository exists and is public
  • Submitter has commit access
  • Assessment re-run passes (±2 points tolerance)
  • JSON schema valid

Automated validation will run on this PR.


Submitted via agentready submit command.

Summary by CodeRabbit

  • New Features
    • Added assessment reporting with comprehensive evaluation findings, scoring metrics, certification levels, and remediation guidance.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 28, 2026

📝 Walkthrough

Walkthrough

This PR adds a machine-generated Konflux CI assessment report for the konflux-ui repository. The JSON file documents evaluation results across multiple attributes, capturing pass/fail statuses, measured values, remediation guidance for failures, and the configuration and runtime metrics used during the assessment.

Changes

Assessment Report

Layer / File(s) Summary
Assessment schema and repository context
submissions/konflux-ci/konflux-ui/2026-05-28T20-22-45-assessment.json
JSON schema version, agent execution metadata, repository identification (branch, commit, language statistics), and overall score with certification level assigned.
Attribute findings and remediation guidance
submissions/konflux-ci/konflux-ui/2026-05-28T20-22-45-assessment.json
Findings array with evaluations of repository attributes, including pass/fail status, measured values, thresholds, evidence, and—for failing checks—remediation steps, tools, and example commands.
Evaluation configuration and runtime metrics
submissions/konflux-ci/konflux-ui/2026-05-28T20-22-45-assessment.json
Evaluation weights, excluded attributes, language settings, output directory configuration, report theme, execution duration in seconds, and discovered skills list.

Possibly related PRs

  • ambient-code/agentready#343: Adds a similar machine-generated Konflux CI assessment JSON artifact with the same findings/config/metadata structure, demonstrating a pattern of released assessment submissions.

Suggested labels

released

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title does not follow Conventional Commits format (type(scope): description). It uses a descriptive label format instead of the required type prefix. Rewrite the title using Conventional Commits format, such as 'chore(leaderboard): add konflux-ci/konflux-ui assessment (82.6/100 - Gold)' to match requirements.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
✨ Simplify code
  • Create PR with simplified code

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@StanislavJochman StanislavJochman marked this pull request as draft May 28, 2026 20:25
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@submissions/konflux-ci/konflux-ui/2026-05-28T20-22-45-assessment.json`:
- Line 6: The JSON fields "assessment_timestamp" and "timestamp" are using
timezone-less ISO strings; update the code that serializes these fields so it
emits timezone-aware date-time values (e.g., append 'Z' or include an explicit
offset) to conform to the date-time schema. Locate where "assessment_timestamp"
and "timestamp" are assigned/serialized in the submission generation logic and
change the formatter to use UTC ISO strings (toISOString or equivalent) or
otherwise include timezone info before writing the JSON output.
- Around line 8-10: The report contains sensitive local identity and absolute
paths in the JSON keys "executed_by", "command", and "working_directory"; update
the code that generates/writes the assessment (the serializer that produces
these JSON fields) to redact or replace user/host names and absolute filesystem
paths with sanitized values (e.g., replace user@host with "<REDACTED_USER>",
strip repo-root prefixes or use relative paths, and replace full binary paths
with basenames or "<REDACTED_PATH>"); ensure the same redaction is applied
wherever those keys are emitted (also for the occurrences referenced at lines 13
and 135) so committed reports never contain raw local identities or absolute
paths.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: e17b57fa-6aa5-44f0-aa3e-f826e81ba54d

📥 Commits

Reviewing files that changed from the base of the PR and between 51e57e7 and 78160ae.

📒 Files selected for processing (1)
  • submissions/konflux-ci/konflux-ui/2026-05-28T20-22-45-assessment.json

"metadata": {
"agentready_version": "2.41.1",
"research_version": "2.0.1",
"assessment_timestamp": "2026-05-28T22:22:24.516105",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Use timezone-aware timestamps to match the report contract consistently.

assessment_timestamp and top-level timestamp are missing timezone (Z/offset). Schema format is date-time; timezone-less values are a common interoperability failure point across validators/parsers.

As per coding guidelines, prioritize Critical and Major severity issues.

Also applies to: 29-29

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@submissions/konflux-ci/konflux-ui/2026-05-28T20-22-45-assessment.json` at
line 6, The JSON fields "assessment_timestamp" and "timestamp" are using
timezone-less ISO strings; update the code that serializes these fields so it
emits timezone-aware date-time values (e.g., append 'Z' or include an explicit
offset) to conform to the date-time schema. Locate where "assessment_timestamp"
and "timestamp" are assigned/serialized in the submission generation logic and
change the formatter to use UTC ISO strings (toISOString or equivalent) or
otherwise include timezone info before writing the JSON output.

Comment on lines +8 to +10
"executed_by": "sjochman@sjochman1-mac",
"command": "/Users/sjochman/git_workspace/RedHat/agentready/src/agentready/__main__.py assess /Users/sjochman/git_workspace/RedHat/konflux-ui --config /Users/sjochman/git_workspace/RedHat/konflux-ui/.agentready-config.yaml",
"working_directory": "/Users/sjochman/git_workspace/RedHat/agentready"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Redact host/user and absolute path data before committing reports.

This report leaks local identity and environment details (executed_by, working_directory, absolute repo path, and full command path). That is a compliance/privacy risk for a committed artifact and can also expose internal workstation topology.

Suggested redaction pattern
- "executed_by": "sjochman@sjochman1-mac",
+ "executed_by": "redacted",
- "command": "/Users/sjochman/.../__main__.py assess /Users/sjochman/.../konflux-ui --config /Users/sjochman/.../.agentready-config.yaml",
+ "command": "agentready assess <repo> --config <config>",
- "working_directory": "/Users/sjochman/git_workspace/RedHat/agentready"
+ "working_directory": "<redacted>"
...
- "path": "/Users/sjochman/git_workspace/RedHat/konflux-ui",
+ "path": "<redacted>"
...
- "CLAUDE.md found at /Users/sjochman/git_workspace/RedHat/konflux-ui/CLAUDE.md"
+ "CLAUDE.md found at <repo>/CLAUDE.md"

As per coding guidelines, prioritize Critical and Major severity issues.

Also applies to: 13-13, 135-135

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@submissions/konflux-ci/konflux-ui/2026-05-28T20-22-45-assessment.json` around
lines 8 - 10, The report contains sensitive local identity and absolute paths in
the JSON keys "executed_by", "command", and "working_directory"; update the code
that generates/writes the assessment (the serializer that produces these JSON
fields) to redact or replace user/host names and absolute filesystem paths with
sanitized values (e.g., replace user@host with "<REDACTED_USER>", strip
repo-root prefixes or use relative paths, and replace full binary paths with
basenames or "<REDACTED_PATH>"); ensure the same redaction is applied wherever
those keys are emitted (also for the occurrences referenced at lines 13 and 135)
so committed reports never contain raw local identities or absolute paths.

@github-actions
Copy link
Copy Markdown
Contributor

Leaderboard Validation

FAILED

Claimed: 82.6/100
Verified: 63.2/100
Diff: 19.4 points (±2 tolerance)

@github-actions
Copy link
Copy Markdown
Contributor

📈 Test Coverage Report

Branch Coverage
This PR 73.1%
Main 73.1%
Diff ✅ +0%

Coverage calculated from unit tests only

Copy link
Copy Markdown
Contributor

@jwm4 jwm4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment from Bill Murdock with assistance from Claude Code

The CI validate check is failing because of a score mismatch (claimed 82.6, actual 63.2). After investigating, there are two factors:

  1. Branch: The assessment was run on the KFLUXUI-1275 feature branch, but the leaderboard validation workflow clones the default branch. Several attributes that pass on the feature branch (single-file verification, one-command setup, issue/PR templates, gitignore completeness, dependency security, file size limits) fail on the default branch.

  2. Config file: The assessment used --config .agentready-config.yaml to exclude 8 inapplicable attributes, which changes the scoring denominator. The validation workflow runs without a config, so those attributes get assessed (and skipped/failed), pulling the score down.

Running with a custom config is often the right thing to do. It lets you focus on the attributes that matter for your project and ignore ones that don't apply. The score you get that way is useful for tracking your own progress, it just won't match what the leaderboard validation produces since it runs the default configuration against the repo's primary branch.

A few options going forward:

  • Re-run against the default branch without a config to get a score that matches what CI will validate
  • Wait for KFLUXUI-1275 to merge, then resubmit against the default branch
  • Keep using the config for your own assessments and skip the leaderboard submission for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants