← Home

@enso-ui/loader

npm Repository Homepage

Loaders, overlays, and skeleton placeholders for Enso UI

7
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

loadervuebulma

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/framework dep referenced in SFC config, not directly imported; stable pattern for this package. ai
phantom-deps phantom-dep:bulma AI (phantom-deps): Bulma is a CSS framework referenced in styles/config, not JS imports; stable pattern for this package. ai
phantom-deps phantom-dep:@enso-ui/transitions AI (phantom-deps): Same-org dep used in Vue SFC template; phantom detection is a false positive here. ai

Versions (showing 7 of 7)

Version Deps Published
4.2.2 0 / 3
4.2.1 0 / 3
4.2.0 0 / 3
4.1.4 0 / 3
4.1.3 0 / 3
4.1.1 3 / 0
4.1.0 3 / 0

v4.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.

v4.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.3

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.

v4.1.1

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.

v4.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.