@buerokratt-ria/header ISC 15 versions

@buerokratt-ria/header

npm

Generic Header component that would be injected as dependency.

15

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ahmed.yasservarmohbuerokrattrasmuseimlatrevordevtailorjannostern

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
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	2026/05/28
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	2026/05/28

Versions (showing 15 of 15)

Version	Deps	Published
0.1.52	3 / 4	2026-06-01
0.1.51	3 / 4	2026-05-11
0.1.50	3 / 4	2026-04-28
0.1.49	3 / 4	2026-04-28
0.1.48	3 / 4	2026-04-20
0.1.47	3 / 4	2025-12-29
0.1.42	3 / 4	2025-10-22
0.1.41	3 / 4	2025-10-21
0.1.40	3 / 4	2025-10-15
0.1.39	3 / 4	2025-08-21
0.1.38	3 / 4	2025-07-24
0.1.37	3 / 4	2025-07-11
0.1.36	3 / 4	2025-05-20
0.1.35	3 / 4	2025-05-08
0.1.34	3 / 4	2025-05-06

v0.1.52

1 finding

LOW No provenance attestation provenance

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

v0.1.51

1 finding

LOW No provenance attestation provenance

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

v0.1.49

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

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

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

1 finding

LOW No provenance attestation provenance

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

v0.1.41

1 finding

LOW No provenance attestation provenance

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

v0.1.40

1 finding

LOW No provenance attestation provenance

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

v0.1.39

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

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

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

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

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

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.