← Home

@hubspot/ts-export-types

npm

Analyze public export types to extract simplified API types a TypeScript packages

5
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

camdenphalenbandersonalsorberdeen-hubspotharminder01bkrainer-hsjhilkeratanasiukksvirkou-hubspotkbreeman-hubspotbrodgers16jsinesservice-ccstfinley_hsjyeager_hubspotarota-hubspothemangthakkarmshannon_hspsteeleidem-hsamead_hsjnorthridge_hubspotelingyrtscalesrsegurajonmiller_hsjedeen-hsbmatto_hsjblake_hubspothweaverhubspotankimobreesebrwilsonbent0b0xbash-hsasun1234blamattina_hubspotchiragchadhajazzyclimberjmcdermott

Keywords

typescripttypesapiexportsanalyzerdocumentationschema

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): HubSpot internal tooling package; provenance gap is a process issue, not a security signal for this package. ai

Versions (showing 5 of 5)

Version Deps Published
1.1.0 2 / 8
1.0.2 2 / 8
1.0.1 2 / 8
1.0.0 2 / 6
0.1.2 2 / 6

v1.0.2

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: psteeleidem-hs.

LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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

v0.1.2

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.