← Home

@synerise/ds-app-menu

AppMenu UI Component for the Synerise Design System

58
Versions
ISC
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

synerise

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established Synerise DS monorepo package; provenance not used across the suite. ai

Versions (showing 58 of 58)

Version Deps Published
1.2.24 4 / 0
1.2.23 4 / 0
1.2.22 4 / 0
1.2.21 4 / 0
1.2.20 4 / 0
1.2.19 4 / 0
1.2.18 4 / 0
1.2.17 4 / 0
1.2.16 4 / 0
1.2.15 4 / 0
1.2.14 4 / 0
1.2.13 4 / 0
1.2.12 4 / 0
1.2.11 4 / 0
1.2.10 4 / 0
1.2.9 4 / 0
1.2.8 4 / 0
1.2.7 4 / 0
1.2.6 4 / 0
1.2.5 4 / 0
1.2.4 4 / 0
1.2.3 4 / 0
1.2.2 4 / 0
1.2.1 4 / 0
1.2.0 4 / 0
1.1.6 4 / 0
1.1.5 4 / 0
1.1.4 4 / 0
1.1.3 4 / 0
1.1.2 4 / 0
1.1.1 4 / 0
1.1.0 4 / 0
1.0.25 4 / 0
1.0.24 4 / 0
1.0.23 4 / 0
1.0.22 4 / 0
1.0.21 4 / 0
1.0.20 4 / 0
1.0.19 4 / 0
1.0.18 4 / 0
1.0.17 4 / 0
1.0.16 4 / 0
1.0.15 4 / 0
1.0.14 4 / 0
1.0.13 4 / 0
1.0.12 4 / 0
1.0.11 4 / 0
1.0.10 4 / 0
1.0.9 4 / 0
1.0.8 4 / 0
1.0.7 4 / 0
1.0.6 4 / 0
1.0.5 4 / 0
1.0.4 4 / 0
1.0.3 4 / 0
1.0.2 4 / 0
1.0.1 4 / 0
1.0.0 4 / 0

v1.2.24

1 finding
INFO No provenance attestation provenance

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

v1.0.6

1 finding
INFO No provenance attestation provenance

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

v1.0.5

1 finding
INFO No provenance attestation provenance

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

v1.0.4

1 finding
INFO No provenance attestation provenance

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

v1.0.3

1 finding
INFO No provenance attestation provenance

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

v1.0.2

1 finding
INFO No provenance attestation provenance

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

v1.0.1

1 finding
INFO No provenance attestation provenance

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

v1.0.0

1 finding
INFO No provenance attestation provenance

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