← Home

@hubspot/serverless-dev-runtime

A tool for testing HubSpot CMS serverless functions locally

5
Versions
Apache-2.0
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-hubspotkbreeman-hubspotbrodgers16jsinesservice-ccstfinley_hsjyeager_hubspotarota-hubspothemangthakkarmshannon_hspsteeleidem-hsamead_hsjnorthridge_hubspotelingyrtscalesrsegurajonmiller_hsjedeen-hsbmatto_hsjblake_hubspothweaverhubspotbash-hsasun1234blamattina_hubspotchiragchadhajazzyclimberjmcdermott

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): HubSpot internal team rotation; no code changes accompany the change. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with internal handoff, not a takeover pattern. ai
publish-pattern dormant-publish AI (publish-pattern): Established official package resuming normal release cadence. ai
semgrep semgrep:child-process-import AI (semgrep): Dev runtime tool legitimately spawns processes; stable pattern across versions. ai
semgrep semgrep:dynamic-require AI (semgrep): Loads user-defined serverless function files by path — core feature of this tool. ai

Versions (showing 5 of 5)

Version Deps Published
7.0.7 11 / 4
7.0.6 10 / 4
7.0.2 10 / 4
7.0.1 10 / 4
7.0.0 10 / 4

v7.0.2

1 finding
LOW No provenance attestation provenance

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

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

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