botframework-connector
1
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
botframeworksgellockcwhitten
Keywords
botconnectorbotschatbots
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): buffer is a browser polyfill explicitly excluded from depcheck in package.json scripts; its phantom status is intentional and documented. | ai | |
| phantom-deps | phantom-dep:@types/jsonwebtoken | AI (phantom-deps): @types/jsonwebtoken is a TypeScript type package used at compile time; phantom status is expected for type-only dependencies in this framework. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft Bot Framework package; lack of Sigstore provenance is consistent across all versions and is not a risk signal for this publisher. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 4.23.3 | 16 / 6 |
v4.23.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.