← Home

@buerokratt-ria/menu

npm

Generic MainNavigation component that would be injected as dependency.

25
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

ahmed.yasservarmohbuerokrattrasmuseimlatrevordevtailorjannostern

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/react AI (phantom-deps): Types package, not directly imported by design. ai
phantom-deps phantom-dep:@buerokratt-ria/styles AI (phantom-deps): Same org scoped package, loaded by convention. ai

Versions (showing 25 of 25)

Version Deps Published
0.2.15 3 / 2
0.2.14 3 / 2
0.2.13 3 / 2
0.2.12 3 / 2
0.2.11 3 / 2
0.2.10 3 / 2
0.2.9 3 / 2
0.2.8 3 / 2
0.2.7 3 / 2
0.2.6 3 / 2
0.2.5 3 / 2
0.2.4 3 / 2
0.2.3 3 / 2
0.2.2 3 / 2
0.2.0 3 / 2
0.1.16 3 / 2
0.1.15 3 / 2
0.1.14 3 / 2
0.1.13 3 / 2
0.1.12 3 / 2
0.1.11 3 / 2
0.1.10 3 / 2
0.1.9 3 / 2
0.1.8 3 / 2
0.1.7 3 / 2

v0.2.7

1 finding
LOW No provenance attestation provenance

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

v0.2.6

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vassili.m → ahmed.yasser (on 2025-02-05, known maintainer) provenance

This version was published by a different npm account (ahmed.yasser) than the most recent previously approved version (vassili.m) on 2025-02-05, but ahmed.yasser is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ahmed.yasser → vassili.m (on 2024-12-23, known maintainer) provenance

This version was published by a different npm account (vassili.m) than the most recent previously approved version (ahmed.yasser) on 2024-12-23, but vassili.m is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: baha-a → ahmed.yasser (on 2024-11-20, known maintainer) provenance

This version was published by a different npm account (ahmed.yasser) than the most recent previously approved version (baha-a) on 2024-11-20, but ahmed.yasser is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.0

2 findings
HIGH Publisher changed: baha-a → sepasass (on 2024-08-19) provenance

This version was published by a different npm account than previous versions on 2024-08-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.16

1 finding
LOW No provenance attestation provenance

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

v0.1.15

1 finding
LOW No provenance attestation provenance

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

v0.1.14

1 finding
LOW No provenance attestation provenance

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

v0.1.13

1 finding
LOW No provenance attestation provenance

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

v0.1.12

1 finding
LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.10

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

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