← Home

@pipedream/statuspage

npm Homepage

Pipedream Statuspage Components

4
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

sacerdoticasrettjkdylburgeradolfo-pddanpipedreamjasonatpipedreamalan-pipedream

Keywords

pipedreamstatuspage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@pipedream/platform AI (dependencies): First-party Pipedream dependency; stable cross-version false positive for this package family. ai
provenance no-provenance AI (provenance): Pipedream org packages consistently lack Sigstore provenance; stable false positive for this package family. ai

Versions (showing 4 of 4)

Version Deps Published
0.3.0 1 / 0
0.2.0 1 / 0
0.1.0 1 / 0
0.0.4 1 / 0

v0.3.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.1.0

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.

v0.0.4

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.