← Home

@enso-ui/progress-indicator

npm Repository Homepage

Threshold and percentage indicators for Enso UI.

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

aocneanugandescvlad.chvraftx24manuela.mindroc

Keywords

progress-indicatorvue

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:vue AI (phantom-deps): Vue is a peer/build dependency in a Vue component library; not directly imported in source is expected. ai
phantom-deps phantom-dep:javascript-color-gradient AI (phantom-deps): Used in component config/build context; phantom-dep pattern is stable for this UI library. ai
phantom-deps phantom-dep:@fortawesome/vue-fontawesome AI (phantom-deps): FontAwesome Vue plugin; declared and used via config-level imports, stable pattern. ai
phantom-deps phantom-dep:@fortawesome/fontawesome-svg-core AI (phantom-deps): FontAwesome core; declared and used via config-level imports, stable pattern. ai
phantom-deps phantom-dep:@fortawesome/free-solid-svg-icons AI (phantom-deps): FontAwesome icons; declared and used via config-level imports, stable pattern. ai

Versions (showing 3 of 3)

Version Deps Published
2.2.2 3 / 1
2.2.0 5 / 0
2.1.0 5 / 0

v2.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.