@hubspot/app-functions-dev-server

A tool for testing HubSpot private app functions locally

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-hubspotkbreeman-hubspotbrodgers16jsinesservice-ccsevdavis_hubspottfinley_hsjyeager_hubspotarota-hubspothemangthakkarmshannon_hspsteeleidem-hsamead_hsjnorthridge_hubspotelingyrtscalesrsegurajonmiller_hsjedeen-hsbmatto_hsjblake_hubspothweaverhubspotankimobreesebrwilsonbent0b0xbash-hsasun1234blamattina_hubspotchiragchadhajazzyclimberjmcdermott

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:cors	AI (phantom-deps): Standard express middleware; likely missed by import scan on compiled dist output.	ai	2026/07/25
phantom-deps	phantom-dep:express	AI (phantom-deps): Core server framework for this dev-server tool; false positive from scan.	ai	2026/07/25
phantom-deps	phantom-dep:uuid	AI (phantom-deps): Common utility dep, used in compiled dist; scan limitation not malicious.	ai	2026/07/25
provenance	publisher-changed	AI (provenance): Internal HubSpot org account transition, publisher has strong clean track record.	ai	2026/07/12
maintainer-change	maintainer-removed	AI (maintainer-change): Routine internal maintainer rotation, not a takeover pattern.	ai	2026/07/12
maintainer-change	maintainer-added	AI (maintainer-change): Known HubSpot org maintainer addition, no behavioral change.	ai	2026/07/12
publish-pattern	new-deps-added	AI (publish-pattern): moment is a well-known, widely-used dependency.	ai	2026/07/12
publish-pattern	dormant-publish	AI (publish-pattern): Established package with slow release cadence, no other malicious signal.	ai	2026/07/12
phantom-deps	phantom-dep:body-parser	AI (phantom-deps): body-parser used indirectly via express config; stable false positive.	ai	2026/07/12

Versions (showing 41 of 41)

Version	Deps	Published
0.11.2	6 / 17	2026-02-23
0.11.1	10 / 19	2026-01-28
0.11.0	9 / 19	2025-12-22
0.10.2	9 / 19	2025-12-03
0.10.1	8 / 12	2025-09-16
0.10.0	8 / 12	2025-08-27
0.9.2	8 / 12	2025-06-24
0.9.0	7 / 12	2025-05-29
0.8.56	7 / 12	2025-05-22
0.8.50	7 / 12	2025-04-01
0.8.48	7 / 12	2025-03-20
0.8.47	7 / 12	2025-03-19
0.8.46	7 / 12	2025-03-14
0.8.43	7 / 12	2025-02-07
0.8.42	7 / 12	2025-01-27
0.8.41	7 / 12	2025-01-16
0.8.40	7 / 12	2025-01-08
0.8.39	8 / 13	2024-12-13
0.8.38	8 / 13	2024-12-09
0.8.37	8 / 13	2024-11-27
0.8.31	7 / 13	2024-08-28
0.8.30	7 / 13	2024-08-26
0.8.28	7 / 13	2024-07-19
0.8.20	7 / 13	2024-05-16
0.8.19	7 / 13	2024-05-14
0.8.18	7 / 13	2024-05-13
0.8.17	7 / 13	2024-05-08
0.8.16	7 / 13	2024-05-01
0.8.15	7 / 13	2024-04-25
0.8.14	7 / 13	2024-04-24
0.8.11	5 / 12	2024-03-05
0.8.9	6 / 12	2024-01-31
0.8.7	6 / 12	2024-01-11
0.8.3	6 / 12	2023-11-16
0.8.2	6 / 12	2023-10-27
0.8.0	5 / 12	2023-10-05
0.7.3	5 / 12	2023-08-23
0.7.2	5 / 12	2023-08-09
0.7.0	4 / 12	2023-08-03
0.6.0	4 / 12	2023-07-31
0.5.0	4 / 12	2023-07-25

v0.10.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 → hweaverhubspot (on 2025-09-16, known maintainer) provenance

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

2 findings

HIGH Publisher changed: rsegura → 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.48

2 findings

HIGH Publisher changed: rsegura → hweaverhubspot (on 2025-03-20) provenance

This version was published by a different npm account than previous versions on 2025-03-20. 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.47

2 findings

HIGH Publisher changed: rsegura → hweaverhubspot (on 2025-03-19) provenance

This version was published by a different npm account than previous versions on 2025-03-19. 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: rsegura → 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 (rsegura) 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.43

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 → banderson (on 2025-02-07, known maintainer) provenance

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

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 → banderson (on 2025-01-27, known maintainer) provenance

This version was published by a different npm account (banderson) than the most recent previously approved version (rsegura) on 2025-01-27, 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.41

1 finding

LOW No provenance attestation provenance

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

v0.8.40

1 finding

LOW No provenance attestation provenance

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

v0.8.39

1 finding

LOW No provenance attestation provenance

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

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

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

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 → rsegura (on 2024-08-26, known maintainer) provenance

This version was published by a different npm account (rsegura) than the most recent previously approved version (jyeager_hubspot) on 2024-08-26, 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.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: jyeager_hubspot → rsegura (on 2024-07-19, known maintainer) provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

1 finding

LOW No provenance attestation provenance

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

v0.8.14

1 finding

LOW No provenance attestation provenance

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

v0.8.11

1 finding

LOW No provenance attestation provenance

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

v0.8.9

1 finding

LOW No provenance attestation provenance

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

v0.8.7

1 finding

LOW No provenance attestation provenance

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

v0.8.3

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 → jyeager_hubspot (on 2023-11-16, known maintainer) provenance

This version was published by a different npm account (jyeager_hubspot) than the most recent previously approved version (banderson) on 2023-11-16, but jyeager_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.

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

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.