@synerise/ds-page-header ISC 51 versions

@synerise/ds-page-header

npm Repository

Page-Header UI Component for the Synerise Design System

51

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

synerise

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@synerise/ds-utils	AI (phantom-deps): @synerise/ds-utils is a declared runtime dep in package.json; same-org scope, stable false positive.	ai	2026/05/17
dependencies	unvetted-dep:@synerise/ds-icon	AI (dependencies): Internal sibling package from same Synerise design system org; expected dependency pattern.	ai	2026/05/17
dependencies	unvetted-dep:@synerise/ds-button	AI (dependencies): Internal sibling package from same Synerise design system org; expected dependency pattern.	ai	2026/05/17
dependencies	unvetted-dep:@synerise/ds-tooltip	AI (dependencies): Internal sibling package from same Synerise design system org; expected dependency pattern.	ai	2026/05/17
dependencies	unvetted-dep:@synerise/ds-typography	AI (dependencies): Internal sibling package from same Synerise design system org; expected dependency pattern.	ai	2026/05/17
dependencies	unvetted-dep:@synerise/ds-inline-edit	AI (dependencies): Internal sibling package from same Synerise design system org; expected dependency pattern.	ai	2026/05/17

Versions (showing 51 of 73)

View all versions

Version	Deps	Published
1.0.81	5 / 0	2026-05-27
1.0.80	5 / 0	2026-05-26
1.0.79	5 / 0	2026-05-22
1.0.78	5 / 0	2026-05-15
1.0.77	5 / 0	2026-05-13
1.0.76	5 / 0	2026-05-11
1.0.75	5 / 0	2026-05-06
1.0.74	5 / 0	2026-05-04
1.0.73	5 / 0	2026-04-29
1.0.72	5 / 0	2026-04-28
1.0.71	5 / 0	2026-04-24
1.0.70	5 / 0	2026-04-22
1.0.69	5 / 0	2026-04-22
1.0.68	5 / 0	2026-04-21
1.0.67	5 / 0	2026-04-14
1.0.66	5 / 0	2026-04-10
1.0.65	5 / 0	2026-04-01
1.0.64	5 / 0	2026-03-24
1.0.63	5 / 0	2026-03-23
1.0.62	5 / 0	2026-03-09
1.0.61	5 / 0	2026-02-26
1.0.60	5 / 0	2026-02-23
1.0.59	5 / 0	2026-02-19
1.0.58	5 / 0	2026-02-12
1.0.57	5 / 0	2026-02-11
1.0.56	5 / 0	2026-02-10
1.0.55	5 / 0	2026-02-10
1.0.54	5 / 0	2026-02-06
1.0.53	5 / 0	2026-02-05
1.0.52	5 / 0	2026-02-02
1.0.51	5 / 0	2026-01-29
1.0.50	5 / 0	2026-01-22
1.0.49	5 / 0	2026-01-21
1.0.48	5 / 0	2026-01-20
1.0.47	5 / 0	2026-01-15
1.0.46	5 / 0	2026-01-12
1.0.45	5 / 0	2026-01-07
1.0.44	5 / 0	2025-12-19
1.0.43	5 / 0	2025-12-16
1.0.42	5 / 0	2025-12-15
1.0.41	5 / 0	2025-11-28
1.0.40	5 / 0	2025-11-13
1.0.39	5 / 0	2025-11-06
1.0.38	5 / 0	2025-10-31
1.0.37	5 / 0	2025-10-22
1.0.36	5 / 0	2025-10-16
1.0.35	5 / 0	2025-10-10
1.0.34	5 / 0	2025-10-08
1.0.33	5 / 0	2025-10-03
1.0.32	5 / 0	2025-09-30
1.0.30	5 / 0	2025-09-26

v1.0.81

1 finding

LOW No provenance attestation provenance

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

v1.0.80

1 finding

LOW No provenance attestation provenance

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

v1.0.79

1 finding

LOW No provenance attestation provenance

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

v1.0.78

1 finding

LOW No provenance attestation provenance

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

v1.0.77

1 finding

LOW No provenance attestation provenance

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

v1.0.76

1 finding

LOW No provenance attestation provenance

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

v1.0.75

1 finding

LOW No provenance attestation provenance

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

v1.0.74

1 finding

LOW No provenance attestation provenance

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

v1.0.73

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.

v1.0.72

1 finding

LOW No provenance attestation provenance

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

v1.0.71

1 finding

LOW No provenance attestation provenance

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

v1.0.70

1 finding

LOW No provenance attestation provenance

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

v1.0.69

1 finding

LOW No provenance attestation provenance

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

v1.0.68

1 finding

LOW No provenance attestation provenance

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

v1.0.67

1 finding

LOW No provenance attestation provenance

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

v1.0.66

1 finding

LOW No provenance attestation provenance

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

v1.0.65

1 finding

LOW No provenance attestation provenance

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

v1.0.64

1 finding

LOW No provenance attestation provenance

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

v1.0.63

1 finding

LOW No provenance attestation provenance

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

v1.0.62

1 finding

LOW No provenance attestation provenance

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

v1.0.61

1 finding

LOW No provenance attestation provenance

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

v1.0.60

1 finding

LOW No provenance attestation provenance

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

v1.0.59

1 finding

LOW No provenance attestation provenance

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

v1.0.58

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.

v1.0.57

1 finding

LOW No provenance attestation provenance

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

v1.0.56

1 finding

LOW No provenance attestation provenance

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

v1.0.55

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.

v1.0.54

1 finding

LOW No provenance attestation provenance

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

v1.0.53

1 finding

LOW No provenance attestation provenance

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

v1.0.52

1 finding

LOW No provenance attestation provenance

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

v1.0.51

1 finding

LOW No provenance attestation provenance

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

v1.0.50

1 finding

LOW No provenance attestation provenance

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

v1.0.49

1 finding

LOW No provenance attestation provenance

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

v1.0.48

1 finding

LOW No provenance attestation provenance

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

v1.0.47

1 finding

LOW No provenance attestation provenance

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

v1.0.46

1 finding

LOW No provenance attestation provenance

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

v1.0.45

1 finding

LOW No provenance attestation provenance

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

v1.0.44

1 finding

LOW No provenance attestation provenance

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

v1.0.43

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.

v1.0.42

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.

v1.0.41

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.

v1.0.40

1 finding

LOW No provenance attestation provenance

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

v1.0.39

1 finding

LOW No provenance attestation provenance

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

v1.0.38

1 finding

LOW No provenance attestation provenance

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

v1.0.37

1 finding

LOW No provenance attestation provenance

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

v1.0.36

1 finding

LOW No provenance attestation provenance

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

v1.0.35

1 finding

LOW No provenance attestation provenance

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

v1.0.34

1 finding

LOW No provenance attestation provenance

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

v1.0.33

1 finding

LOW No provenance attestation provenance

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

v1.0.32

1 finding

LOW No provenance attestation provenance

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

v1.0.30

1 finding

LOW No provenance attestation provenance

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