@pipedream/github
Pipedream GitHub 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo publish quirk from trusted publisher; no behavior change in diff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-level maintainer roster churn, not a takeover signal given clean diff. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes GitHub API file content (response.content) — standard GitHub REST API pattern, not obfuscation. | ai | |
| dependencies | unvetted-dep:@octokit/webhooks-definitions | AI (dependencies): Official Octokit package from the GitHub org; well-known and expected for GitHub integrations. | ai | |
| dependencies | unvetted-dep:@pipedream/platform | AI (dependencies): Core Pipedream platform dep; stable and expected for all @pipedream/* packages. | 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 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 4 / 0 | |
| 3.0.0 | 4 / 0 | |
| 2.0.0 | 4 / 0 | |
| 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.11.1 | 4 / 0 | |
| 1.11.0 | 4 / 0 | |
| 1.10.0 | 4 / 0 | |
| 1.9.0 | 4 / 0 | |
| 1.8.4 | 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 | |
| 1.7.0 | 4 / 0 | |
| 1.6.2 | 4 / 0 | |
| 1.6.1 | 4 / 0 | |
| 1.6.0 | 4 / 0 | |
| 1.5.0 | 4 / 0 | |
| 1.4.1 | 4 / 0 | |
| 1.4.0 | 4 / 0 | |
| 1.3.0 | 4 / 0 | |
| 1.2.2 | 4 / 0 | |
| 1.2.1 | 4 / 0 | |
| 1.2.0 | 4 / 0 |
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adolfo-pd) than the most recent previously approved version (casret) on 2026-03-17, but adolfo-pd 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.
v1.10.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adolfo-pd) than the most recent previously approved version (casret) on 2025-12-31, but adolfo-pd 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.
v1.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: casret.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: casret.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: casret.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: casret.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.