← Home

@enso-ui/menus

Menu management pages and sidebar/menu components for Enso UI

21
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

menusvue

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@enso-ui/forms AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for component libraries with indirect usage. ai
phantom-deps phantom-dep:@enso-ui/tables AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for component libraries with indirect usage. ai
phantom-deps phantom-dep:@enso-ui/dropdown-indicator AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for component libraries with indirect usage. ai
phantom-deps phantom-dep:vue AI (phantom-deps): Vue is a peer/config-level dep for Vue component packages; not directly imported in source is expected. ai
phantom-deps phantom-dep:@enso-ui/switch AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for component libraries with indirect usage. ai
phantom-deps phantom-dep:@fortawesome/vue-fontawesome AI (phantom-deps): Referenced in config files only; stable false positive for this UI component package. ai
phantom-deps phantom-dep:vuedraggable AI (phantom-deps): Referenced in config/template files only; stable false positive for this UI component package. ai

Versions (showing 21 of 21)

Version Deps Published
5.2.28 4 / 12
5.2.27 4 / 12
5.2.26 4 / 12
5.2.24 4 / 12
5.2.21 4 / 12
5.2.20 4 / 12
5.2.19 4 / 12
5.2.18 4 / 12
5.2.17 4 / 11
5.2.16 4 / 8
5.2.15 4 / 8
5.2.14 4 / 8
5.2.13 4 / 8
5.2.12 4 / 7
5.2.11 4 / 7
5.2.9 4 / 7
5.2.8 4 / 7
5.2.7 4 / 7
5.2.6 4 / 7
5.2.0 11 / 0
5.1.0 11 / 0

v5.2.28

1 finding
LOW No provenance attestation provenance

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

v5.2.27

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

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v5.2.9

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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