← Home

@hubspot/ui-extensions

npm
80
Versions
—
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_hsbmadgettmjeanjevensonuserkrysbvandyckjblake_hubspothweaverhubspotankimobreesebrwilsonbent0b0xbash-hsasun1234blamattina_hubspotchiragchadhajazzyclimberjmcdermott

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Internal HubSpot account handoff; publisher has clean 281-package track record. ai
maintainer-change maintainer-removed AI (maintainer-change): Routine maintainer rotation within trusted org. ai
maintainer-change maintainer-added AI (maintainer-change): HubSpot official org rotates maintainers frequently; no compromise indicators. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Established HubSpot package; 0.0.0 is a monorepo versioning quirk, not throwaway malware. ai
publish-pattern new-deps-added AI (publish-pattern): Companion @remote-ui testing lib, consistent with existing @remote-ui/react dependency. ai
dependencies unvetted-dep:@remote-ui/testing AI (dependencies): @remote-ui/testing is a Shopify-maintained testing utility; its use here is consistent with the package's testing exports. ai
dependencies unvetted-dep:@remote-ui/react AI (dependencies): @remote-ui/react is a known Shopify open-source library; stable dep for this package. ai
dependencies unvetted-dep:@remote-ui/core AI (dependencies): @remote-ui/core is a known Shopify open-source library; stable dep for this package. ai
bogus-package bogus-package AI (bogus-package): Corporate scoped SDK; missing repo/keywords/README details are typical for internal HubSpot packages across 99 versions. ai
phantom-deps phantom-dep:react-reconciler AI (phantom-deps): react-reconciler is a declared runtime dep used transitively by @remote-ui/react; phantom-dep heuristic fires but it is legitimately present. ai

Versions (showing 80 of 80)

Version Deps Published
0.15.0 5 / 17
0.14.2 5 / 17
0.14.0 5 / 17
0.13.2 5 / 17
0.13.1 5 / 17
0.13.0 5 / 17
0.12.4 5 / 17
0.12.3 5 / 17
0.12.2 5 / 12
0.12.1 5 / 12
0.12.0 5 / 12
0.11.6 5 / 12
0.11.5 5 / 12
0.11.4 5 / 12
0.11.3 4 / 12
0.11.2 3 / 12
0.11.1 3 / 13
0.11.0 2 / 10
0.9.7 3 / 9
0.9.6 3 / 9
0.9.5 3 / 9
0.9.3 3 / 9
0.9.1 3 / 9
0.9.0 3 / 9
0.8.56 3 / 9
0.8.55 3 / 9
0.8.54 3 / 9
0.8.50 3 / 4
0.8.46 3 / 4
0.8.40 3 / 4
0.8.39 3 / 4
0.8.38 2 / 1
0.8.37 2 / 1
0.8.36 2 / 1
0.8.35 2 / 1
0.8.34 2 / 1
0.8.33 2 / 1
0.8.32 2 / 1
0.8.31 2 / 1
0.8.30 2 / 1
0.8.29 2 / 1
0.8.28 2 / 1
0.8.27 2 / 1
0.8.26 2 / 1
0.8.25 2 / 1
0.8.24 2 / 1
0.8.23 2 / 1
0.8.22 2 / 1
0.8.21 2 / 1
0.8.20 2 / 1
0.8.18 2 / 1
0.8.17 2 / 1
0.8.16 2 / 1
0.8.14 2 / 1
0.8.13 2 / 1
0.8.12 2 / 1
0.8.11 2 / 1
0.8.10 2 / 1
0.8.9 2 / 1
0.8.8 2 / 1
0.8.7 2 / 1
0.8.6 2 / 1
0.8.5 2 / 1
0.8.4 2 / 1
0.8.3 2 / 1
0.8.2 2 / 1
0.8.1 2 / 1
0.8.0 2 / 1
0.7.3 2 / 1
0.7.2 2 / 1
0.7.1 2 / 1
0.7.0 2 / 1
0.6.0 2 / 1
0.5.0 2 / 1
0.4.0 2 / 1
0.3.1 2 / 1
0.3.0 2 / 1
0.2.0 2 / 1
0.1.0 2 / 1
0.0.0 2 / 0

v0.15.0

1 finding
LOW No provenance attestation provenance

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

v0.13.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: evdavis_hubspot → hweaverhubspot (on 2026-04-30, known maintainer) provenance

This version was published by a different npm account (hweaverhubspot) than the most recent previously approved version (evdavis_hubspot) on 2026-04-30, but hweaverhubspot 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.11.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: rsegura → hweaverhubspot (on 2025-10-24, known maintainer) provenance

This version was published by a different npm account (hweaverhubspot) than the most recent previously approved version (rsegura) on 2025-10-24, but hweaverhubspot 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.11.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: rsegura → jedeen-hs (on 2025-10-09, known maintainer) provenance

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

v0.9.6

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: hweaverhubspot → jedeen-hs (on 2025-08-08, known maintainer) provenance

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

v0.8.50

2 findings
HIGH Publisher changed: jedeen-hs → hweaverhubspot (on 2025-04-01) provenance

This version was published by a different npm account than previous versions on 2025-04-01. 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.8.46

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: jedeen-hs → banderson (on 2025-03-14, known maintainer) provenance

This version was published by a different npm account (banderson) than the most recent previously approved version (jedeen-hs) on 2025-03-14, but banderson 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.8.40

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: jedeen-hs → rsegura (on 2025-01-08, known maintainer) provenance

This version was published by a different npm account (rsegura) than the most recent previously approved version (jedeen-hs) on 2025-01-08, but rsegura 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.8.39

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: jedeen-hs → rsegura (on 2024-12-13, known maintainer) provenance

This version was published by a different npm account (rsegura) than the most recent previously approved version (jedeen-hs) on 2024-12-13, but rsegura 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.8.38

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: rsegura → jedeen-hs (on 2024-12-09, known maintainer) provenance

This version was published by a different npm account (jedeen-hs) than the most recent previously approved version (rsegura) on 2024-12-09, but jedeen-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.

v0.8.37

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: jedeen-hs → rsegura (on 2024-11-27, known maintainer) provenance

This version was published by a different npm account (rsegura) than the most recent previously approved version (jedeen-hs) on 2024-11-27, but rsegura 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.8.36

1 finding
LOW No provenance attestation provenance

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

v0.8.35

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: rsegura → jedeen-hs (on 2024-10-03, known maintainer) provenance

This version was published by a different npm account (jedeen-hs) than the most recent previously approved version (rsegura) on 2024-10-03, but jedeen-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.

v0.8.34

1 finding
LOW No provenance attestation provenance

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

v0.8.33

1 finding
LOW No provenance attestation provenance

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

v0.8.32

1 finding
LOW No provenance attestation provenance

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

v0.8.31

1 finding
LOW No provenance attestation provenance

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

v0.8.30

1 finding
LOW No provenance attestation provenance

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

v0.8.29

1 finding
LOW No provenance attestation provenance

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

v0.8.28

1 finding
LOW No provenance attestation provenance

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

v0.8.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: banderson → rsegura (on 2024-07-10, known maintainer) provenance

This version was published by a different npm account (rsegura) than the most recent previously approved version (banderson) on 2024-07-10, but rsegura 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.8.26

1 finding
LOW No provenance attestation provenance

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

v0.8.25

1 finding
LOW No provenance attestation provenance

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

v0.8.24

1 finding
LOW No provenance attestation provenance

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

v0.8.23

1 finding
LOW No provenance attestation provenance

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

v0.8.22

1 finding
LOW No provenance attestation provenance

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

v0.8.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: jyeager_hubspot → banderson (on 2024-05-28, known maintainer) provenance

This version was published by a different npm account (banderson) than the most recent previously approved version (jyeager_hubspot) on 2024-05-28, but banderson 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.8.20

1 finding
LOW No provenance attestation provenance

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

v0.8.18

1 finding
LOW No provenance attestation provenance

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

v0.8.17

1 finding
LOW No provenance attestation provenance

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

v0.8.16

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

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

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

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

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

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

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

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

v0.8.5

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.