@activepieces/piece-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ai-sdk/replicate | AI (phantom-deps): Monorepo workspace package; shared deps declared at root level. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/anthropic | AI (phantom-deps): Monorepo workspace package; shared deps declared at root level. | ai | |
| phantom-deps | phantom-dep:ai | AI (phantom-deps): Monorepo workspace package; shared deps declared at root level, not directly imported in this piece. | ai | |
| phantom-deps | phantom-dep:fast-glob | AI (phantom-deps): Monorepo workspace package; shared deps declared at root level. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google | AI (phantom-deps): Monorepo workspace package; shared deps declared at root level. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): Monorepo workspace package; shared deps declared at root level. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Monorepo shared config pattern. | ai | |
| phantom-deps | phantom-dep:axios-retry | AI (phantom-deps): Monorepo shared config pattern. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Monorepo shared config pattern. | ai | |
| phantom-deps | phantom-dep:@sinclair/typebox | AI (phantom-deps): Monorepo shared config pattern. | ai | |
| phantom-deps | phantom-dep:deepmerge-ts | AI (phantom-deps): Monorepo shared config pattern. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Monorepo shared config pattern; deps inherited from workspace root, not direct imports. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Monorepo shared config pattern. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Monorepo shared config pattern. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Monorepo shared config pattern. | ai | |
| phantom-deps | phantom-dep:form-data | AI (phantom-deps): Monorepo shared config pattern. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding Microsoft Graph API email attachment contentBytes — standard pattern for this package's purpose. | ai | |
| phantom-deps | phantom-dep:@microsoft/microsoft-graph-types | AI (phantom-deps): Type-only dependency; not imported at runtime but used for TypeScript type definitions — stable false positive. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.3.5 | 7 / 0 | |
| 0.3.4 | 7 / 0 | |
| 0.3.3 | 7 / 0 | |
| 0.3.2 | 9 / 0 | |
| 0.3.1 | 9 / 0 | |
| 0.3.0 | 9 / 0 | |
| 0.2.14 | 7 / 0 | |
| 0.2.13 | 7 / 0 | |
| 0.2.12 | 7 / 0 | |
| 0.2.11 | 7 / 0 | |
| 0.2.10 | 7 / 0 | |
| 0.2.9 | 7 / 0 | |
| 0.2.8 | 5 / 0 | |
| 0.2.7 | 18 / 0 | |
| 0.2.6 | 19 / 0 | |
| 0.2.5 | 19 / 0 | |
| 0.2.4 | 19 / 0 | |
| 0.2.3 | 21 / 0 | |
| 0.2.2 | 18 / 0 | |
| 0.2.1 | 18 / 0 | |
| 0.2.0 | 17 / 0 | |
| 0.1.14 | 15 / 0 | |
| 0.1.13 | 15 / 0 | |
| 0.1.12 | 15 / 0 | |
| 0.1.11 | 16 / 0 | |
| 0.1.10 | 16 / 0 | |
| 0.1.9 | 16 / 0 | |
| 0.1.8 | 16 / 0 | |
| 0.1.7 | 16 / 0 | |
| 0.1.6 | 16 / 0 | |
| 0.1.5 | 22 / 0 | |
| 0.1.4 | 21 / 0 | |
| 0.1.3 | 21 / 0 | |
| 0.1.2 | 21 / 0 | |
| 0.1.1 | 21 / 0 | |
| 0.1.0 | 21 / 0 | |
| 0.0.1 | 20 / 0 |
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.