@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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: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 | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Same pattern as axios; declared dependency used via config references in Pipedream component structure. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.13.0 | 11 / 0 | |
| 1.12.0 | 11 / 0 | |
| 1.11.3 | 11 / 0 | |
| 1.10.0 | 11 / 0 | |
| 1.9.0 | 11 / 0 | |
| 1.7.10 | 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.2 | 5 / 0 | |
| 1.5.4 | 5 / 0 | |
| 1.5.2 | 5 / 0 | |
| 1.5.1 | 5 / 0 |
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.