@pipedream/gitlab
Pipedream Gitlab Components
5
Versions
—
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
sacerdoticasrettjkdylburgeradolfo-pddanpipedreamjasonatpipedreamalan-pipedream
Keywords
pipedreamgitlab
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Pipedream org package with verified publisher track record; dormancy reflects org publishing cadence, not account takeover risk. | ai | |
| dependencies | unvetted-dep:@pipedream/platform | AI (dependencies): First-party Pipedream dependency used consistently across all Pipedream component packages. | ai | |
| provenance | no-provenance | AI (provenance): Pipedream org packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 3 / 0 | |
| 0.8.0 | 3 / 0 | |
| 0.7.0 | 3 / 0 | |
| 0.6.0 | 3 / 0 | |
| 0.5.6 | 3 / 0 |
v0.9.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.