Skip to content

feat(landing): explain automated plugin checks - #146

Merged
777genius merged 1 commit into
mainfrom
feat/security-assessment-details
Sep 5, 2026
Merged

feat(landing): explain automated plugin checks#146
777genius merged 1 commit into
mainfrom
feat/security-assessment-details

Conversation

@777genius

@777genius 777genius commented Sep 5, 2026

Copy link
Copy Markdown
Owner

What changed

  • replace the generic warning badge with a calmer automated review summary
  • bind the badge and tooltip to the exact indexed revision and preview real findings
  • add a detailed security review section to community plugin pages
  • separate install-relevant concerns from GitHub Actions maintenance notes without changing signed outcomes
  • explain how newer upstream revisions are re-indexed and rechecked

Verification

  • pnpm run test:registry - 21 passed
  • pnpm run lint - passed
  • pnpm run generate - passed against Directory 33, Discovery 38, Security 3
  • Playwright landing.spec.ts - 23 passed using local Chrome

Summary by CodeRabbit

  • New Features
    • Added security assessment badges to plugin listings, including scan status, revision details, tooltips, and links to full reviews.
    • Added a security review section to community plugin pages with scan outcomes, findings, dates, locations, and installation guidance.
    • Added responsive layouts and status-specific styling for security review information.
  • Bug Fixes
    • Improved security messaging by distinguishing notes from blocking findings and clarifying that reviews do not guarantee plugin safety.

@coderabbitai

coderabbitai Bot commented Sep 5, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 817d0b70-f1dc-4154-ad46-6a8a6d87449a

📥 Commits

Reviewing files that changed from the base of the PR and between 1a2d77e and 78236b5.

📒 Files selected for processing (8)
  • landing/assets/styles/registry.scss
  • landing/components/registry/RegistryPluginCard.vue
  • landing/components/registry/SecurityAssessmentBadge.vue
  • landing/components/registry/SecurityAssessmentPanel.vue
  • landing/pages/plugins/community.vue
  • landing/tests/browser/landing.spec.ts
  • landing/tests/securityPresentation.test.ts
  • landing/utils/securityPresentation.ts

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The landing page now uses shared security presentation helpers, reusable assessment badges, and a security review panel. Plugin badges link to profile review sections. The panel displays outcomes, revisions, findings, freshness notices, and safety guidance.

Changes

Security assessment review

Layer / File(s) Summary
Security presentation helpers and tests
landing/utils/securityPresentation.ts, landing/tests/securityPresentation.test.ts
Classifies findings, groups installer and maintainer findings, formats assessment labels and tooltips, and tests these behaviors.
Assessment badge navigation
landing/components/registry/RegistryPluginCard.vue, landing/components/registry/SecurityAssessmentBadge.vue, landing/assets/styles/registry.scss, landing/tests/browser/landing.spec.ts
Replaces inline card markup with a reusable linked badge and adds security review anchor navigation.
Plugin security review panel
landing/components/registry/SecurityAssessmentPanel.vue, landing/pages/plugins/community.vue, landing/assets/styles/registry.scss, landing/tests/browser/landing.spec.ts
Renders assessment metadata, findings, revision notices, disclaimers, responsive styles, and browser coverage for the review section.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Merge Risk: ⚪ Minimal · up to 78236

This change adds linked automated-review summaries and detailed plugin security-review information without changing signed outcomes. The updated presentation and navigation paths are covered, with no current merge-blocking risk identified.

Sequence Diagram(s)

sequenceDiagram
  participant RegistryPluginCard
  participant SecurityAssessmentBadge
  participant CommunityPluginPage
  participant SecurityAssessmentPanel
  RegistryPluginCard->>SecurityAssessmentBadge: pass plugin and securityDetailURL
  SecurityAssessmentBadge->>CommunityPluginPage: navigate to `#security-review`
  CommunityPluginPage->>SecurityAssessmentPanel: render plugin security assessment
  SecurityAssessmentPanel->>SecurityAssessmentPanel: group findings and render review details
Loading

Poem

A rabbit checks the badge with care
Then hops to findings waiting there
Revisions shine in tidy rows
Notes and warnings neatly pose
“No safety promise,” softly goes
The carrot-powered review now grows

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 3 files. (5 skipped: 5 … Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: explaining automated plugin checks on the landing page.
Description check ✅ Passed The description clearly explains the changes and includes concrete verification results. It omits the required Release Impact section and checklist formatting, but it is otherwise mostly complete and …
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.
Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 3 files. (5 skipped: 5 unsupported.)

  • Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/security-assessment-details

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.

@777genius
777genius merged commit a46ac43 into main Sep 5, 2026
17 checks passed
@777genius
777genius deleted the feat/security-assessment-details branch September 5, 2026 14:35
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.

1 participant