@pipedream/hubspot
Pipedream Hubspot Components
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Pipedream internal team rotation; new maintainers are org accounts with clean track records. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Pipedream internal team rotation; removal of prior org maintainers is consistent with normal team changes. | ai | |
| dependencies | unvetted-dep:timezones-list | AI (dependencies): timezones-list is a benign IANA timezone data package; no malicious history and appropriate for HubSpot integration use. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Pipedream org package with consistent publisher track record; dormancy reflects component maintenance cadence, not takeover risk. | ai | |
| dependencies | unvetted-dep:@pipedream/platform | AI (dependencies): First-party Pipedream dependency; stable and expected across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Pipedream packages consistently lack provenance attestation; stable false positive for this package family. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 1.18.2 | 3 / 1 | |
| 1.18.1 | 3 / 1 | |
| 1.18.0 | 3 / 1 | |
| 1.17.0 | 2 / 1 | |
| 1.16.4 | 2 / 1 | |
| 1.16.3 | 2 / 1 | |
| 1.16.2 | 2 / 1 | |
| 1.16.1 | 2 / 1 | |
| 1.16.0 | 2 / 1 | |
| 1.15.0 | 2 / 1 | |
| 1.14.0 | 2 / 1 | |
| 1.13.1 | 2 / 1 | |
| 1.13.0 | 2 / 1 | |
| 1.12.1 | 2 / 1 | |
| 1.12.0 | 2 / 1 | |
| 1.11.1 | 2 / 1 | |
| 1.11.0 | 2 / 1 | |
| 1.10.0 | 2 / 1 | |
| 1.9.0 | 2 / 1 | |
| 1.8.2 | 2 / 1 | |
| 1.8.1 | 2 / 1 | |
| 1.8.0 | 2 / 1 | |
| 1.7.15 | 2 / 1 | |
| 1.7.14 | 2 / 1 | |
| 1.7.12 | 2 / 1 | |
| 1.7.11 | 2 / 1 | |
| 1.7.10 | 2 / 1 | |
| 1.7.9 | 2 / 1 | |
| 1.7.8 | 2 / 1 | |
| 1.7.7 | 2 / 1 | |
| 1.7.6 | 2 / 1 | |
| 1.7.5 | 2 / 1 | |
| 1.7.4 | 2 / 1 | |
| 1.7.3 | 2 / 1 | |
| 1.7.2 | 2 / 1 | |
| 1.7.1 | 2 / 1 | |
| 1.7.0 | 2 / 1 | |
| 1.6.4 | 2 / 1 | |
| 1.6.3 | 2 / 1 | |
| 1.6.2 | 2 / 1 | |
| 1.6.1 | 2 / 1 | |
| 1.6.0 | 2 / 1 | |
| 1.5.0 | 2 / 1 | |
| 1.4.0 | 2 / 1 | |
| 1.3.1 | 2 / 1 | |
| 1.3.0 | 2 / 1 | |
| 1.2.4 | 2 / 1 | |
| 1.2.3 | 2 / 1 | |
| 1.2.2 | 2 / 1 | |
| 1.2.1 | 2 / 1 | |
| 1.2.0 | 2 / 1 | |
| 1.1.0 | 2 / 1 | |
| 1.0.2 | 2 / 1 | |
| 1.0.1 | 2 / 1 | |
| 1.0.0 | 2 / 1 |
v1.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.