← Home

@twilio/flex-sdk

3
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

twilio-agent-connect-maintainerstwilio-supply-chainbaderboland

Keywords

flexsdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:buffer AI (phantom-deps): buffer is a bundled webpack polyfill in the browser SDK output; no scannable import text — stable FP. ai

Versions (showing 3 of 3)

Version Deps Published
4.1.0 14 / 0
4.0.0 13 / 0
3.1.0 15 / 0

v4.1.0

4 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (twilio-flex-sdk) were replaced by new maintainers (twilio-agent-connect-maintainers, twilio-supply-chain, baderboland). This is a strong signal of a potential package hijack and requires careful review.

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH Publisher changed: twilio-flex-sdk → GitHub Actions (on 2026-07-20) provenance

This version was published by a different npm account than previous versions on 2026-07-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.0

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.

v3.1.0

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.