← Home

@hubspot/create-cms-theme

npm

HubSpot CMS React starter theme

51
Versions
Apache-2.0
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

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Publisher has strong track record (34 approved, 0 rejected); consistent with internal HubSpot handoff. ai
maintainer-change maintainer-removed AI (maintainer-change): Expected when maintainer role transitions within same org. ai
phantom-deps phantom-dep:vitest AI (phantom-deps): vitest referenced in config files only; stable false positive for this package. ai

Versions (showing 51 of 93)

View all versions
Version Deps Published
1.2.57 7 / 2
1.2.56 7 / 2
1.2.53 7 / 2
1.2.50 7 / 2
1.2.49 7 / 2
1.2.47 7 / 2
1.2.46 7 / 2
1.2.45 7 / 2
1.2.44 7 / 2
1.2.42 7 / 2
1.2.41 7 / 2
1.2.40 7 / 2
1.2.39 7 / 2
1.2.38 7 / 2
1.2.36 7 / 2
1.2.35 7 / 2
1.2.34 7 / 2
1.2.33 7 / 2
1.2.32 7 / 2
1.2.31 7 / 2
1.2.30 7 / 2
1.2.29 7 / 2
1.2.28 7 / 2
1.2.27 7 / 2
1.2.26 7 / 2
1.2.25 7 / 2
1.2.24 7 / 2
1.2.23 7 / 2
1.2.22 7 / 2
1.2.21 7 / 2
1.2.20 7 / 2
1.2.19 7 / 2
1.2.18 7 / 2
1.2.17 7 / 2
1.2.16 7 / 2
1.2.15 7 / 2
1.2.13 7 / 2
1.2.12 7 / 2
1.2.9 7 / 2
1.2.7 7 / 2
1.2.6 7 / 2
1.2.2 7 / 2
1.2.1 7 / 2
1.2.0 7 / 2
1.0.65 7 / 2
1.0.64 7 / 2
1.0.63 7 / 2
1.0.62 7 / 2
1.0.61 7 / 2
1.0.55 7 / 2
1.0.54 7 / 2

v1.2.57

1 finding
LOW No provenance attestation provenance

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

v1.2.56

2 findings
HIGH Publisher changed: bmatto_hs → bpuseyhs (on 2026-07-16) provenance

This version was published by a different npm account than previous versions on 2026-07-16. 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.

v1.2.53

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: jonmiller_hs → bmatto_hs (on 2026-07-15, known maintainer) provenance

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

v1.2.50

1 finding
LOW No provenance attestation provenance

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

v1.2.49

1 finding
LOW No provenance attestation provenance

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

v1.2.47

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: jblake_hubspot → jonmiller_hs (on 2026-07-01, known maintainer) provenance

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

v1.2.46

1 finding
LOW No provenance attestation provenance

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

v1.2.45

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 → jblake_hubspot (on 2026-06-30, known maintainer) provenance

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

v1.2.44

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 → jonmiller_hs (on 2026-06-26, known maintainer) provenance

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

v1.2.35

1 finding
LOW No provenance attestation provenance

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

v1.2.34

1 finding
LOW No provenance attestation provenance

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

v1.2.33

1 finding
LOW No provenance attestation provenance

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

v1.2.32

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

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

v1.2.31

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

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

v1.2.30

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

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

v1.2.29

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

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

v1.2.28

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: jrosa838 → jmcdermott (on 2026-05-01, known maintainer) provenance

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

v1.2.26

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

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

v1.2.23

1 finding
LOW No provenance attestation provenance

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

v1.2.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: jmcdermott → jrosa838 (on 2026-03-26, known maintainer) provenance

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

v1.2.21

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: amead_hs → jmcdermott (on 2026-03-20, known maintainer) provenance

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

v1.2.20

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: amead_hs → jmcdermott (on 2026-03-19, known maintainer) provenance

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

v1.2.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: amead_hs → jonmiller_hs (on 2026-03-16, known maintainer) provenance

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

v1.2.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: jonmiller_hs → amead_hs (on 2026-03-11, known maintainer) provenance

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

v1.2.17

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: jblake_hubspot → jonmiller_hs (on 2026-02-25, known maintainer) provenance

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

v1.2.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: jonmiller_hs → jblake_hubspot (on 2026-02-20, known maintainer) provenance

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

v1.2.15

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: jonmiller_hs → jblake_hubspot (on 2026-02-20, known maintainer) provenance

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

v1.2.12

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: amead_hs → bmatto_hs (on 2026-02-10, known maintainer) provenance

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

v1.2.9

1 finding
LOW No provenance attestation provenance

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

v1.2.7

1 finding
LOW No provenance attestation provenance

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

v1.2.6

1 finding
LOW No provenance attestation provenance

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

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.2.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: jonmiller_hs → amead_hs (on 2025-12-08, known maintainer) provenance

This version was published by a different npm account (amead_hs) than the most recent previously approved version (jonmiller_hs) on 2025-12-08, but amead_hs 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.

v1.2.0

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: jonmiller_hs → bmatto_hs (on 2025-12-03, known maintainer) provenance

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

v1.0.62

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: bmatto_hs → amead_hs (on 2025-10-24, known maintainer) provenance

This version was published by a different npm account (amead_hs) than the most recent previously approved version (bmatto_hs) on 2025-10-24, but amead_hs 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.

v1.0.61

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: jonmiller_hs → bmatto_hs (on 2025-10-15, known maintainer) provenance

This version was published by a different npm account (bmatto_hs) than the most recent previously approved version (jonmiller_hs) on 2025-10-15, but bmatto_hs 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.

v1.0.55

1 finding
LOW No provenance attestation provenance

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

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.