← Home

@enso-ui/localisation

23
Versions
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

localisationvue

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@enso-ui/transitions AI (phantom-deps): Same-org peer dep used in templates/config, not direct JS import; expected pattern. ai
phantom-deps phantom-dep:@enso-ui/dropdown AI (phantom-deps): Same-org peer dep used in templates/config, not direct JS import; expected pattern. ai
phantom-deps phantom-dep:@enso-ui/directives AI (phantom-deps): Same-org peer dep used in templates/config, not direct JS import; expected pattern. ai
phantom-deps phantom-dep:vue AI (phantom-deps): Vue is a peer dep for a Vue component library; not directly imported in JS is expected. ai
phantom-deps phantom-dep:flag-icon-css AI (phantom-deps): CSS-only library referenced in config/templates, not JS imports; stable pattern for this package. ai
phantom-deps phantom-dep:@enso-ui/forms AI (phantom-deps): Same-org peer dep used in templates/config, not direct JS import; expected pattern. ai
phantom-deps phantom-dep:@enso-ui/select AI (phantom-deps): Same-org peer dep used in templates/config, not direct JS import; expected pattern. ai
phantom-deps phantom-dep:@enso-ui/switch AI (phantom-deps): Same-org peer dep used in templates/config, not direct JS import; expected pattern. ai
phantom-deps phantom-dep:@enso-ui/tables AI (phantom-deps): Same-org peer dep used in templates/config, not direct JS import; expected pattern. ai
phantom-deps phantom-dep:@fortawesome/vue-fontawesome AI (phantom-deps): Vue component library dependency referenced in config; not directly imported in JS but legitimately used. ai
phantom-deps phantom-dep:flag-icons AI (phantom-deps): flag-icons is a CSS asset dependency used via config/styles, not direct JS imports; stable pattern for this UI package. ai

Versions (showing 23 of 23)

Version Deps Published
5.2.24 4 / 16
5.2.23 4 / 16
5.2.21 4 / 16
5.2.20 4 / 16
5.2.19 4 / 16
5.2.18 4 / 16
5.2.17 4 / 16
5.2.16 4 / 13
5.2.15 4 / 12
5.2.14 4 / 12
5.2.13 4 / 12
5.2.12 4 / 11
5.2.10 4 / 10
5.2.8 4 / 10
5.2.7 4 / 10
5.2.6 12 / 2
5.2.5 14 / 0
5.2.4 14 / 0
5.2.3 14 / 0
5.2.2 14 / 0
5.2.1 14 / 0
5.2.0 14 / 0
5.1.0 14 / 0

v5.2.24

1 finding
LOW No provenance attestation provenance

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

v5.2.21

1 finding
LOW No provenance attestation provenance

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

v5.2.20

1 finding
LOW No provenance attestation provenance

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

v5.2.19

1 finding
LOW No provenance attestation provenance

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

v5.2.18

1 finding
LOW No provenance attestation provenance

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

v5.2.17

1 finding
LOW No provenance attestation provenance

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

v5.2.16

1 finding
LOW No provenance attestation provenance

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

v5.2.15

1 finding
LOW No provenance attestation provenance

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

v5.2.14

1 finding
LOW No provenance attestation provenance

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

v5.2.13

1 finding
LOW No provenance attestation provenance

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

v5.2.12

1 finding
LOW No provenance attestation provenance

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

v5.2.10

1 finding
LOW No provenance attestation provenance

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

v5.2.8

1 finding
LOW No provenance attestation provenance

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

v5.2.7

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.

v5.2.6

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.

v5.2.5

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.

v5.2.4

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.

v5.2.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.

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

v5.2.1

1 finding
LOW No provenance attestation provenance

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

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

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