@hubspot/cms-dev-server
Local dev server for JS rendering
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@storybook/testing-library | AI (phantom-deps): Storybook config-only reference; stable phantom-dep pattern for this dev-server package. | ai | |
| source-diff | obfuscated-file:dist/app/assets/index-BhmkOPU4.js | AI (source-diff): Standard Vite-bundled React UI asset; minification is expected for this CMS dev server package. | ai | |
| source-diff | obfuscated-file:dist/app/assets/index-tvg7JxpD.js | AI (source-diff): Vite-bundled React UI asset; minified output is expected for this dev-server package. | ai | |
| provenance | publisher-changed | AI (provenance): Both accounts are HubSpot org publishers; internal maintainer rotation, not a takeover signal. | ai | |
| source-diff | obfuscated-file:dist/app/assets/index-CEoO7aJ5.js | AI (source-diff): Standard Vite-bundled React UI asset; minification is expected for this CMS dev server package. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): Deprecated but not malicious; stable pattern in this long-lived HubSpot package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal HubSpot tooling package; sparse metadata is consistent across its 197-version history. | ai | |
| dependencies | unvetted-dep:vite-plugin-mkcert | AI (dependencies): vite-plugin-mkcert is a well-known Vite SSL plugin; no malicious history; pinned to 1.16.0. | ai | |
| phantom-deps | phantom-dep:@storybook/react-vite | AI (phantom-deps): Declared runtime dep used via storybook config. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-toggle | AI (phantom-deps): Declared runtime dep; likely loaded indirectly via component registry. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-links | AI (phantom-deps): Declared runtime dep used via storybook config. | ai | |
| phantom-deps | phantom-dep:storybook | AI (phantom-deps): Declared runtime dep used via storybook config convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-essentials | AI (phantom-deps): Declared runtime dep used via storybook config. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-interactions | AI (phantom-deps): Declared runtime dep used via storybook config. | ai | |
| phantom-deps | phantom-dep:babel-plugin-styled-components | AI (phantom-deps): Declared runtime dep used via babel config convention. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-actions | AI (phantom-deps): Declared runtime dep used via storybook config. | ai | |
| phantom-deps | phantom-dep:styled-jsx | AI (phantom-deps): Declared runtime dep loaded by framework convention. | ai | |
| phantom-deps | phantom-dep:@storybook/test | AI (phantom-deps): Declared runtime dep used via storybook config. | ai | |
| phantom-deps | phantom-dep:@storybook/react | AI (phantom-deps): Declared runtime dep used via storybook config. | ai | |
| phantom-deps | phantom-dep:@babel/code-frame | AI (phantom-deps): Framework-scoped package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:babel-plugin-macros | AI (phantom-deps): Declared runtime dep used via babel config convention. | ai | |
| phantom-deps | phantom-dep:tailwindcss-animate | AI (phantom-deps): Declared runtime dep referenced in tailwind config. | ai | |
| phantom-deps | phantom-dep:vite-plugin-inspect | AI (phantom-deps): Declared runtime dep used via vite config convention. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.2.36 | 50 / 15 | |
| 1.2.35 | 50 / 15 | |
| 1.2.34 | 50 / 15 | |
| 1.2.33 | 50 / 15 | |
| 1.2.32 | 50 / 15 | |
| 1.2.31 | 50 / 15 | |
| 1.2.30 | 50 / 15 | |
| 1.2.28 | 50 / 15 | |
| 1.2.27 | 50 / 15 | |
| 1.2.26 | 50 / 15 | |
| 1.2.25 | 50 / 15 | |
| 1.2.24 | 50 / 15 | |
| 1.2.23 | 50 / 15 | |
| 1.2.22 | 50 / 15 | |
| 1.2.21 | 50 / 15 | |
| 1.2.20 | 50 / 15 | |
| 1.2.19 | 50 / 15 | |
| 1.2.18 | 50 / 15 | |
| 1.2.17 | 50 / 15 | |
| 1.2.16 | 50 / 15 | |
| 1.2.13 | 50 / 15 | |
| 1.2.12 | 50 / 15 | |
| 1.2.9 | 50 / 15 | |
| 1.2.7 | 50 / 15 | |
| 1.2.6 | 50 / 15 | |
| 1.2.2 | 50 / 15 | |
| 1.2.1 | 50 / 15 | |
| 1.2.0 | 50 / 15 | |
| 1.0.47 | 50 / 15 | |
| 1.0.46 | 50 / 15 | |
| 1.0.45 | 50 / 15 | |
| 1.0.44 | 50 / 15 | |
| 1.0.43 | 50 / 15 | |
| 1.0.38 | 51 / 15 | |
| 1.0.30 | 49 / 15 | |
| 1.0.29 | 49 / 15 |
v1.2.36
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jonmiller_hs) than the most recent previously approved version (amead_hs) on 2026-05-28, 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
3 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.34
3 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.33
3 findingsThis version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.32
3 findingsThis version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.31
3 findingsThis version was published by a different npm account than previous versions on 2026-05-11. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.30
3 findingsThis version was published by a different npm account than previous versions on 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.28
3 findingsThis version was published by a different npm account than previous versions on 2026-05-01. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.27
3 findingsThis version was published by a different npm account than previous versions on 2026-04-27. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.22
3 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
3 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
3 findingsThis 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.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
3 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. 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.
v1.2.16
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. 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.
v1.2.13
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. 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.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-03. 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.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.