← Home

@pipedream/github

npm Homepage

Pipedream GitHub Components

12
Versions
—
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

sacerdoticasrettjkdylburgeradolfo-pddanpipedreamjasonatpipedreamalan-pipedream

Keywords

pipedreamgithub

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@pipedream/platform AI (dependencies): Core Pipedream platform dep; stable and expected for all @pipedream/* packages. ai
dependencies unvetted-dep:@octokit/webhooks-definitions AI (dependencies): Official Octokit package from the GitHub org; well-known and expected for GitHub integrations. ai
publish-pattern dormant-publish AI (publish-pattern): Pipedream org package with clean publisher history; dormancy consistent with infrequent but legitimate maintenance cadence. ai
phantom-deps phantom-dep:@octokit/webhooks-definitions AI (phantom-deps): Used in config files rather than direct imports; stable false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
1.16.0 4 / 0
1.15.0 4 / 0
1.14.0 4 / 0
1.13.0 4 / 0
1.12.0 4 / 0
1.9.0 4 / 0
1.8.3 4 / 0
1.8.2 4 / 0
1.8.1 4 / 0
1.8.0 4 / 0
1.7.2 4 / 0
1.7.1 4 / 0

v1.16.0

1 finding
LOW No provenance attestation provenance

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

v1.15.0

1 finding
LOW No provenance attestation provenance

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

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

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

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

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

v1.8.3

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.

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

v1.8.1

1 finding
LOW No provenance attestation provenance

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

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

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

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