@hubspot/cms-component-library

HubSpot CMS React component library for building CMS modules

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

camdenphalenbandersonalsorberdeen-hubspotharminder01bkrainer-hsjhilkeratanasiukksvirkou-hubspotbrodgers16jsinesservice-ccsevdavis_hubspottfinley_hsjyeager_hubspotarota-hubspothemangthakkarmshannon_hspsteeleidem-hsamead_hsjnorthridge_hubspotelingyrtscalesrseguraakuhl-hubspotjonmiller_hsjrosa838joeydjedeen-hsbmatto_hsbmadgettmjeanbpuseyhsjevensonuserkrysbvandyckjblake_hubspothweaverhubspotankimobreesebrwilsonbent0b0xbash-hsasun1234blamattina_hubspotjazzyclimberjmcdermott

Keywords

hubspotcmsreactcomponentstypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): New publisher has strong track record (91 approved, 0 rejected); no behavioral change in diff.	ai	2026/07/06
provenance	missing-githead	AI (provenance): Internal HubSpot publish infra variance; no behavioral change in diff.	ai	2026/07/06
maintainer-change	maintainer-added	AI (maintainer-change): Likely internal team rotation at HubSpot; no other compromise indicators.	ai	2026/07/06
publish-pattern	new-deps-added	AI (publish-pattern): Legitimate carousel library swap, well-known npm packages.	ai	2026/07/06
phantom-deps	phantom-dep:sass-embedded	AI (phantom-deps): Used via config/build tooling, not direct import; expected for sass.	ai	2026/07/06

Versions (showing 49 of 49)

Version	Deps	Published
0.5.2	6 / 5	2026-07-17
0.5.1	6 / 5	2026-07-16
0.5.0	6 / 5	2026-07-15
0.4.3	6 / 5	2026-07-13
0.4.2	6 / 5	2026-07-01
0.4.1	6 / 5	2026-06-29
0.4.0	6 / 5	2026-06-29
0.3.39	5 / 5	2026-06-26
0.3.38	5 / 5	2026-06-22
0.3.37	5 / 5	2026-06-17
0.3.36	5 / 5	2026-06-17
0.3.35	5 / 4	2026-06-03
0.3.34	5 / 4	2026-05-29
0.3.33	3 / 4	2026-05-26
0.3.32	3 / 4	2026-05-19
0.3.31	3 / 4	2026-05-14
0.3.30	3 / 4	2026-05-13
0.3.29	3 / 4	2026-05-12
0.3.28	3 / 4	2026-05-11
0.3.27	3 / 4	2026-05-08
0.3.26	3 / 4	2026-04-29
0.3.25	3 / 4	2026-04-29
0.3.24	3 / 4	2026-04-29
0.3.23	3 / 4	2026-04-28
0.3.22	3 / 4	2026-04-27
0.3.21	3 / 4	2026-04-23
0.3.20	3 / 4	2026-04-21
0.3.19	3 / 4	2026-04-21
0.3.18	3 / 4	2026-04-15
0.3.17	3 / 4	2026-04-14
0.3.16	3 / 4	2026-04-10
0.3.15	3 / 4	2026-04-09
0.3.14	3 / 3	2026-04-09
0.3.13	3 / 3	2026-04-03
0.3.12	3 / 3	2026-04-01
0.3.11	3 / 3	2026-03-30
0.3.10	3 / 3	2026-03-30
0.3.9	3 / 3	2026-03-30
0.3.8	2 / 4	2026-03-19
0.3.7	2 / 4	2026-03-17
0.3.6	2 / 4	2026-03-16
0.3.5	2 / 4	2026-03-06
0.3.4	2 / 4	2026-03-05
0.3.3	2 / 4	2026-03-04
0.3.2	2 / 4	2026-03-03
0.3.1	3 / 3	2026-02-26
0.3.0	3 / 3	2026-02-23
0.2.0	3 / 3	2026-02-20
0.1.0	3 / 3	2026-01-08

v0.5.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: joeyd → jrosa838 (on 2026-07-17, known maintainer) provenance

This version was published by a different npm account (jrosa838) than the most recent previously approved version (joeyd) on 2026-07-17, but jrosa838 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.5.1

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: joeyd → jrosa838 (on 2026-07-16, known maintainer) provenance

This version was published by a different npm account (jrosa838) than the most recent previously approved version (joeyd) on 2026-07-16, but jrosa838 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.5.0

3 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: joeyd.

INFO Publisher changed: jrosa838 → joeyd (on 2026-07-15, known maintainer) provenance

This version was published by a different npm account (joeyd) than the most recent previously approved version (jrosa838) on 2026-07-15, but joeyd 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.4.3

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: jazzyclimber → jrosa838 (on 2026-07-13, known maintainer) provenance

This version was published by a different npm account (jrosa838) than the most recent previously approved version (jazzyclimber) on 2026-07-13, but jrosa838 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.4.2

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-07-01, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-07-01, but jazzyclimber 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.4.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-06-29, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-06-29, but jazzyclimber 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.4.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-06-29, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-06-29, but jazzyclimber 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.3.39

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-06-26, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-06-26, but jazzyclimber 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.3.32

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-05-19, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-05-19, but jazzyclimber 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.3.30

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-05-13, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-05-13, but jazzyclimber 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.3.29

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-05-12, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-05-12, but jazzyclimber 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.3.26

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-04-29, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-04-29, but jazzyclimber 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.3.25

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-04-29, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-04-29, but jazzyclimber 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.3.22

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: jazzyclimber → jrosa838 (on 2026-04-27, known maintainer) provenance

This version was published by a different npm account (jrosa838) than the most recent previously approved version (jazzyclimber) on 2026-04-27, but jrosa838 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.3.21

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-04-23, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-04-23, but jazzyclimber 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.3.20

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

v0.3.19

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

v0.3.18

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

v0.3.17

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

INFO Publisher changed: jrosa838 → jazzyclimber (on 2026-04-14, known maintainer) provenance

This version was published by a different npm account (jazzyclimber) than the most recent previously approved version (jrosa838) on 2026-04-14, but jazzyclimber 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.3.16

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: jazzyclimber → jrosa838 (on 2026-04-10, known maintainer) provenance

This version was published by a different npm account (jrosa838) than the most recent previously approved version (jazzyclimber) on 2026-04-10, but jrosa838 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.3.15

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

v0.3.14

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

v0.3.13

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jazzyclimber.

LOW No provenance attestation provenance

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

v0.3.8

2 findings

HIGH Publisher changed: jazzyclimber → joeyd (on 2026-03-19) provenance

This version was published by a different npm account than previous versions on 2026-03-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.3.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: jazzyclimber → jmcdermott (on 2026-03-06, known maintainer) provenance

This version was published by a different npm account (jmcdermott) than the most recent previously approved version (jazzyclimber) on 2026-03-06, but jmcdermott 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.3.4

2 findings

HIGH Publisher changed: jazzyclimber → jrosa838 (on 2026-03-05) provenance

This version was published by a different npm account than previous versions on 2026-03-05. 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.3.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: jazzyclimber → jmcdermott (on 2026-03-03, known maintainer) provenance

This version was published by a different npm account (jmcdermott) than the most recent previously approved version (jazzyclimber) on 2026-03-03, but jmcdermott 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.