@activepieces/piece-microsoft-teams
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/anthropic | AI (phantom-deps): Config-referenced AI provider variant; stable for this integration. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google | AI (phantom-deps): Config-referenced AI provider variant; stable for this integration. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): Config-referenced AI provider variant; stable for this integration. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/replicate | AI (phantom-deps): Config-referenced AI provider variant; stable for this integration. | ai | |
| phantom-deps | phantom-dep:ai | AI (phantom-deps): Config-referenced AI SDK dependency; stable pattern for this integration package. | ai | |
| phantom-deps | phantom-dep:fast-glob | AI (phantom-deps): Config-referenced build/plugin dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:deepmerge-ts | AI (phantom-deps): Declared and used indirectly via framework; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@sinclair/typebox | AI (phantom-deps): Declared and used indirectly via framework; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:axios-retry | AI (phantom-deps): Declared and used indirectly via framework; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared and used indirectly via framework; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Declared and used indirectly via framework; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Declared and used indirectly via framework; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Declared and used indirectly via framework; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Declared and used indirectly via framework; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:regenerator-runtime | AI (phantom-deps): Regenerator-runtime is a known implicit dependency for async/await; stable pattern. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Babel runtime is a known implicit dependency for transpiled code; stable pattern. | ai | |
| phantom-deps | phantom-dep:@microsoft/microsoft-graph-types | AI (phantom-deps): Declared in dependencies and used via @microsoft/microsoft-graph-client; false positive for scoped packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package; missing metadata is normal for monorepo pieces without independent branding. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.5.3 | 7 / 0 | |
| 0.5.2 | 7 / 0 | |
| 0.5.1 | 7 / 0 | |
| 0.5.0 | 7 / 0 | |
| 0.4.2 | 9 / 0 | |
| 0.4.1 | 9 / 0 | |
| 0.4.0 | 9 / 0 | |
| 0.3.13 | 7 / 0 | |
| 0.3.12 | 7 / 0 | |
| 0.3.11 | 7 / 0 | |
| 0.3.10 | 7 / 0 | |
| 0.3.9 | 7 / 0 | |
| 0.3.8 | 7 / 0 | |
| 0.3.7 | 5 / 0 | |
| 0.3.6 | 18 / 0 | |
| 0.3.5 | 19 / 0 | |
| 0.3.4 | 19 / 0 | |
| 0.3.3 | 19 / 0 | |
| 0.3.2 | 21 / 0 | |
| 0.3.1 | 21 / 0 | |
| 0.3.0 | 17 / 0 | |
| 0.2.3 | 15 / 0 | |
| 0.2.2 | 15 / 0 | |
| 0.2.1 | 15 / 0 | |
| 0.2.0 | 15 / 0 | |
| 0.1.11 | 15 / 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 | 20 / 0 |
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.