← Home

@pipedream/microsoft_outlook_calendar

Pipedream Microsoft Outlook Calendar Components

2
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

pipedreammicrosoft_outlook_calendarmicrosoftoutlook

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Pipedream org packages consistently lack Sigstore provenance; stable false positive for this package family. ai
dependencies unvetted-dep:windows-iana AI (dependencies): Well-known timezone utility; no malicious history. ai
dependencies unvetted-dep:@pipedream/platform AI (dependencies): First-party Pipedream dependency; stable for this package. ai
dependencies unvetted-dep:@pipedream/pipedream AI (dependencies): First-party Pipedream dependency; stable for this package. ai
dependencies unvetted-dep:@pipedream/microsoft_outlook AI (dependencies): First-party Pipedream dependency; stable for this package. ai

Versions (showing 2 of 2)

Version Deps Published
8.2.0 8 / 0
8.0.1 8 / 0

v8.0.1

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.