← Home

@buerokratt-ria/header

npm

Generic Header component that would be injected as dependency.

38
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): Framework-scoped type package; loaded by convention, not direct import. Stable FP for this package. ai
phantom-deps phantom-dep:@buerokratt-ria/styles AI (phantom-deps): Same-org styles dependency; indirect usage pattern is expected for a UI component library. ai

Versions (showing 38 of 38)

Version Deps Published
0.1.53 3 / 4
0.1.52 3 / 4
0.1.51 3 / 4
0.1.50 3 / 4
0.1.49 3 / 4
0.1.48 3 / 4
0.1.47 3 / 4
0.1.42 3 / 4
0.1.41 3 / 4
0.1.40 3 / 4
0.1.39 3 / 4
0.1.38 3 / 4
0.1.37 3 / 4
0.1.36 3 / 4
0.1.35 3 / 4
0.1.34 3 / 4
0.1.33 3 / 4
0.1.32 3 / 4
0.1.31 3 / 4
0.1.30 3 / 4
0.1.29 3 / 4
0.1.28 3 / 4
0.1.27 3 / 4
0.1.26 3 / 4
0.1.25 3 / 4
0.1.24 3 / 4
0.1.22 3 / 4
0.1.21 3 / 4
0.1.20 3 / 4
0.1.19 3 / 4
0.1.18 3 / 4
0.1.17 3 / 4
0.1.14 3 / 4
0.1.10 3 / 4
0.1.9 3 / 4
0.1.8 3 / 2
0.1.7 3 / 2
0.1.6 3 / 2

v0.1.53

1 finding
LOW No provenance attestation provenance

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

v0.1.33

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 → jannostern (on 2025-04-24, known maintainer) provenance

This version was published by a different npm account (jannostern) than the most recent previously approved version (ahmed.yasser) on 2025-04-24, but jannostern 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.1.32

1 finding
LOW No provenance attestation provenance

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

v0.1.31

1 finding
LOW No provenance attestation provenance

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

v0.1.30

1 finding
LOW No provenance attestation provenance

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

v0.1.29

1 finding
LOW No provenance attestation provenance

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

v0.1.28

1 finding
LOW No provenance attestation provenance

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

v0.1.27

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-03-25, 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-03-25, 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.1.26

1 finding
LOW No provenance attestation provenance

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

v0.1.25

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 2025-03-19, known maintainer) provenance

This version was published by a different npm account (vassili.m) than the most recent previously approved version (ahmed.yasser) on 2025-03-19, 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.1.24

1 finding
LOW No provenance attestation provenance

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

v0.1.22

1 finding
LOW No provenance attestation provenance

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

v0.1.21

1 finding
LOW No provenance attestation provenance

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

v0.1.20

1 finding
LOW No provenance attestation provenance

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

v0.1.19

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-01-20, 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-01-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.1.18

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 2025-01-14, known maintainer) provenance

This version was published by a different npm account (vassili.m) than the most recent previously approved version (ahmed.yasser) on 2025-01-14, 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.1.17

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

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-09-30, 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-09-30, 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.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.

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