@hubspot/npm-scripts
Scripts for working with npm packages in the HubSpot ecosystem
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): brodgers16 is a long-standing HubSpot publisher (1306 days, 13 approved packages); transition appears legitimate. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Fires in test assertions verifying expected env passthrough behavior, not in production code paths. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): @inquirer/prompts is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 8 / 17 | |
| 0.2.0 | 8 / 17 | |
| 0.1.1 | 8 / 17 | |
| 0.1.0 | 8 / 16 | |
| 0.0.6 | 7 / 16 | |
| 0.0.5 | 7 / 16 | |
| 0.0.4 | 7 / 16 | |
| 0.0.3 | 7 / 16 | |
| 0.0.2 | 7 / 16 |
v0.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-07. 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.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-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.
v0.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-19. 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.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-10-16. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.