syncfusion-blazor-stepper — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited syncfusion-blazor-stepper (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The Blazor Stepper component provides an intuitive way to guide users through multi-step processes. It displays progress across numbered or labeled steps, supporting linear and non-linear workflows with customizable animations, templates, and validation states.
Use the Stepper component when you need to:
The Stepper displays steps in a horizontal or vertical layout with configurable indicators, labels, and templates. Each step can be customized with:
📄 Read: references/api-reference.md
📄 Read: references/getting-started.md
📄 Read: references/step-types.md
📄 Read: references/events.md
📄 Read: references/templates-and-styling.md
📄 Read: references/advanced-features.md
📄 Read: references/animations-and-globalization.md
📄 Read: references/orientations-and-layouts.md
@using Syncfusion.Blazor.Navigations
<SfStepper>
<StepperSteps>
<StepperStep Label="Cart" IconCss="sf-icon-cart"></StepperStep>
<StepperStep Label="Address" IconCss="sf-icon-transport"></StepperStep>
<StepperStep Label="Payment" IconCss="sf-icon-payment"></StepperStep>
<StepperStep Label="Ordered" IconCss="sf-icon-success"></StepperStep>
</StepperSteps>
</SfStepper>Use the Linear property to enforce sequential progression—users can only move to the next step after completing the current one.
<SfStepper Linear="true">
<!-- Steps -->
</SfStepper>Set the ActiveStep property to control which step is currently active (0-indexed).
<SfStepper ActiveStep="1">
<!-- Steps -->
</SfStepper>Handle the StepChanged event to respond when users navigate between steps.
<SfStepper StepChanged="@OnStepChanged">
<!-- Steps -->
</SfStepper>
@code {
private void OnStepChanged(StepperChangedEventArgs args)
{
// Handle step change
}
}Display success or error states using the IsValid property on individual steps.
<StepperStep Label="Payment" IsValid="true"></StepperStep>
<StepperStep Label="Confirm" IsValid="false"></StepperStep>| Property | Type | Purpose |
|---|---|---|
ActiveStep | int | Sets the currently active step (0-indexed) |
LinearFlow | bool | Enforces sequential step progression |
ReadOnly | bool | Disables user interaction with the stepper |
StepType | StepperType | Display format (Default, Label, Indicator) |
Orientation | StepperOrientation | Layout direction (Horizontal, Vertical) |
LabelPosition | StepperLabelPosition | Label placement (Top, Bottom, Start, End) |
Step Properties:
Label: Display text for the stepText: Alternative text contentIconCss: CSS class for custom iconsDisabled: Prevents interaction with the stepOptional: Marks step as optionalIsValid: Sets validation state (true/false/null)Status: Current state (NotStarted, InProgress, Completed)CssClass: Custom CSS class for stylingCheckout Flow: Guide users through purchase steps with validation and error handling.
Form Wizards: Break complex forms into manageable steps with optional sections.
Onboarding: Create step-by-step tutorials for new users with progress tracking.
Setup Wizards: Guide users through configuration processes with success/error states.
Task Lists: Display checklist-style progress with completed/pending indicators.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.