← Home

@stripe/agent-toolkit

npm Repository Homepage

The Stripe Agent Toolkit enables popular agent frameworks including LangChain and Vercel's AI SDK to integrate with Stripe APIs through function calling.

14
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

nazli-stripestripejsjordand-stripearashn-stripemaxliu-stripehideokamoto-stripejackieosborn-stripebillfinn-stripelins-stripestripe-bindingsjil-stripetomas-stripegraceg-stripebibek-striperado-stripeyuluomengcyuen-stripefkuo-stripetomasf-stripechaves-stripeporter-stripelemuel-stripengrubb-stripecchalstrom-stripecharliecruzan-stripemattpatt-stripeericfrank-stripetomer-stripemindy-stripetennhard-stripejackokerman-stripeianjabour-stripestegs-stripejeremyg-stripeebarrenechea-stripestevekaliski-stripematebek-stripehenryx-stripekovalev-stripeaaronhernandez-stripeaywang-stripetimbennett-stripedavidme-stripekentwilliams-stripesvenugopal-stripealexander-stripetoluo-stripetillh-stripewooj-stripecarlosmuvijoyceqin-stripejaynewstrom-stripegbirch-stripecttsailuisv-stripelamflam-stripetjclawson-stripematv-stripetianzhao-stripelng-stripemats-stripesamer-stripe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Both old and new publishers are Stripe-affiliated accounts; internal team transition, not a takeover. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (tjclawson-stripe, matv-stripe) follow Stripe naming convention; consistent with org-internal handoff. ai

Versions (showing 14 of 14)

Version Deps Published
0.9.0 5 / 16
0.7.12 3 / 16
0.7.11 3 / 16
0.7.10 3 / 16
0.7.9 3 / 16
0.7.8 3 / 16
0.7.7 3 / 16
0.7.6 3 / 16
0.7.5 3 / 16
0.7.4 3 / 16
0.7.3 3 / 16
0.7.2 3 / 16
0.7.1 3 / 16
0.7.0 3 / 16

v0.7.12

2 findings
HIGH Publisher changed: stevekaliski-stripe → matv-stripe (on 2025-10-29) provenance

This version was published by a different npm account than previous versions on 2025-10-29. 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.

v0.7.11

2 findings
HIGH Publisher changed: stevekaliski-stripe → matv-stripe (on 2025-08-13) provenance

This version was published by a different npm account than previous versions on 2025-08-13. 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.

v0.7.10

1 finding
LOW No provenance attestation provenance

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

v0.7.9

1 finding
LOW No provenance attestation provenance

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

v0.7.8

1 finding
LOW No provenance attestation provenance

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

v0.7.7

1 finding
LOW No provenance attestation provenance

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

v0.7.6

1 finding
LOW No provenance attestation provenance

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

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