@hubspot/ui-extensions
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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/core | AI (dependencies): @remote-ui/core is a known Shopify open-source library; stable dep for this package. | 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 | |
| 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 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.14.0 | 5 / 17 | |
| 0.13.2 | 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.0 | 2 / 10 | |
| 0.9.7 | 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 |
v0.14.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hweaverhubspot) than the most recent previously approved version (evdavis_hubspot) on 2026-05-19, 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.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.56
2 findingsThis version was published by a different npm account than previous versions on 2025-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.