@pipedream/microsoft_outlook
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-wide roster update by trusted publisher, no behavioral change in package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Legit libs (pdf/docx/headless-chrome) matching attachment-conversion feature. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher is a known maintainer per provenance record, not a takeover. | ai | |
| dependencies | unvetted-dep:@pipedream/platform | AI (dependencies): First-party Pipedream dependency; stable and expected across all @pipedream/* packages. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Pipedream uses automated CI publishing; rapid successive publishes are normal for this org's packages. | ai | |
| dependencies | unvetted-dep:@sparticuz/chromium | AI (dependencies): Known serverless Chromium package used for PDF/browser automation; consistent with puppeteer-core dependency in this package. | ai | |
| provenance | no-provenance | AI (provenance): Pipedream publishes all its component packages without Sigstore provenance; stable pattern across the org. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 used for email attachment download buffering — standard pattern for this Outlook integration package. | ai | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Same pattern as axios; declared dependency used via config references in Pipedream component structure. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Declared in package.json for use by components; phantom-dep heuristic fires on config-only references in this monorepo-style package. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.15.3 | 11 / 0 | |
| 1.15.2 | 11 / 0 | |
| 1.15.1 | 11 / 0 | |
| 1.15.0 | 11 / 0 | |
| 1.14.1 | 11 / 0 | |
| 1.14.0 | 11 / 0 | |
| 1.13.3 | 11 / 0 | |
| 1.13.2 | 11 / 0 | |
| 1.13.1 | 11 / 0 | |
| 1.13.0 | 11 / 0 | |
| 1.12.0 | 11 / 0 | |
| 1.11.3 | 11 / 0 | |
| 1.11.2 | 11 / 0 | |
| 1.10.2 | 11 / 0 | |
| 1.10.1 | 11 / 0 | |
| 1.10.0 | 11 / 0 | |
| 1.9.3 | 11 / 0 | |
| 1.9.2 | 11 / 0 | |
| 1.9.1 | 11 / 0 | |
| 1.9.0 | 11 / 0 | |
| 1.8.1 | 11 / 0 | |
| 1.8.0 | 10 / 0 | |
| 1.7.10 | 9 / 0 | |
| 1.7.9 | 9 / 0 | |
| 1.7.8 | 5 / 0 | |
| 1.7.7 | 5 / 0 | |
| 1.7.6 | 5 / 0 | |
| 1.7.5 | 5 / 0 | |
| 1.7.4 | 5 / 0 | |
| 1.7.3 | 5 / 0 | |
| 1.7.2 | 5 / 0 | |
| 1.7.1 | 5 / 0 | |
| 1.7.0 | 5 / 0 | |
| 1.6.0 | 5 / 0 | |
| 1.5.5 | 5 / 0 | |
| 1.5.4 | 5 / 0 | |
| 1.5.3 | 5 / 0 | |
| 1.5.2 | 5 / 0 | |
| 1.5.1 | 5 / 0 | |
| 1.5.0 | 5 / 0 | |
| 1.4.1 | 5 / 0 | |
| 1.4.0 | 5 / 0 | |
| 1.3.0 | 5 / 0 | |
| 1.2.0 | 5 / 0 | |
| 1.1.1 | 5 / 0 | |
| 1.1.0 | 5 / 0 | |
| 1.0.5 | 4 / 0 | |
| 1.0.4 | 4 / 0 |
v1.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
2 findings[Accepted risk] Package 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-01-30, 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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.