@telnyx/ai-agent-lib MIT 32 versions

@telnyx/ai-agent-lib

npm

[![npm version](https://img.shields.io/npm/v/@telnyx/ai-agent-lib.svg)](https://www.npmjs.com/package/@telnyx/ai-agent-lib) [![npm downloads](https://img.shields.io/npm/dm/@telnyx/ai-agent-lib.svg)](https://www.npmjs.com/package/@telnyx/ai-agent-lib) [![C

32

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

team-telnyxfrontend-squad-telnyxdanilo-telnyxlucasassisrosarudra-telnyxisaad3v

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:eventemitter3	AI (phantom-deps): Declared runtime dep; likely used transitively or re-exported. Stable false positive for this package.	ai	2026/05/14
phantom-deps	phantom-dep:@telnyx/webrtc	AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic unreliable for peer/re-exported deps.	ai	2026/05/14
phantom-deps	phantom-dep:loglevel	AI (phantom-deps): Declared runtime dep; likely used transitively or re-exported. Stable false positive for this package.	ai	2026/05/14
bogus-package	bogus-package	AI (bogus-package): New library with minimal metadata; not indicative of malice given publisher track record.	ai	2026/05/14
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): React library; react-dom is a standard peer/framework dependency.	ai	2026/05/14
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): Type definitions loaded by convention; stable for this package.	ai	2026/05/14
phantom-deps	phantom-dep:jotai	AI (phantom-deps): jotai is declared in dependencies; phantom-dep heuristic false positive for this package.	ai	2026/05/05
install-scripts	install-script:postinstall	AI (install-scripts): Postinstall runs a local type-fix script for WebRTC types; no network access or arbitrary code execution.	ai	2026/05/05

Versions (showing 32 of 32)

Version	Deps	Published
0.4.6	4 / 19	2026-06-01
0.4.5	4 / 19	2026-05-29
0.4.4	4 / 19	2026-05-11
0.4.3	4 / 19	2026-04-30
0.4.1	4 / 19	2026-04-24
0.4.0	4 / 19	2026-04-24
0.3.4	4 / 19	2026-04-15
0.3.3	4 / 19	2026-04-15
0.3.2	4 / 19	2026-04-15
0.3.1	4 / 19	2026-03-13
0.2.13	4 / 19	2026-02-09
0.2.12	4 / 19	2026-02-03
0.2.11	4 / 19	2026-01-22
0.2.10	4 / 19	2026-01-22
0.2.8	4 / 19	2026-01-22
0.2.6	4 / 19	2026-01-22
0.2.5	4 / 15	2025-12-19
0.2.4	4 / 15	2025-12-16
0.2.3	4 / 15	2025-12-16
0.2.2	4 / 15	2025-12-15
0.2.1	4 / 15	2025-12-15
0.2.0	4 / 15	2025-12-15
0.1.10	3 / 15	2025-12-15
0.1.9	3 / 15	2025-12-01
0.1.7	3 / 15	2025-08-05
0.1.6	3 / 15	2025-08-05
0.1.5	3 / 15	2025-07-29
0.1.4	3 / 15	2025-07-29
0.1.3	3 / 13	2025-07-29
0.1.2	3 / 13	2025-07-29
0.1.1	3 / 13	2025-07-29
0.1.0	6 / 12	2025-07-29

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.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.

v0.4.1

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.

v0.4.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.

v0.3.4

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.

v0.3.3

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/fix-webrtc-types.mjs

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.

v0.3.2

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/fix-webrtc-types.mjs

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.

v0.3.1

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.

v0.2.13

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.

v0.2.12

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.

v0.2.11

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.

v0.2.10

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.

v0.2.8

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.

v0.2.6

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.

v0.2.5

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.

v0.2.4

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.

v0.2.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.

v0.2.2

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.

v0.2.1

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.

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.10

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.

v0.1.9

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.

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.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.

v0.1.2

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.

v0.1.1

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.

v0.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.