stripe@22.6.1
Safe to upgrade.
Older than 72 h, no known advisories, no follow-up hotfix, license and provenance unchanged.
Why this verdict
- Older than 72 h, no known advisories, no follow-up hotfix, license and provenance unchanged.Evidence
Confidence 100% · algorithm v1 · computed 2026-10-19. How verdicts work
Supply chain and security
- Malware reports
- None known (OSV)
- Known advisories
- None known (OSV)
- License
- MIT
- Install scripts
- None
- Build provenance
- Signed provenance
- Weekly downloads
- 229,177
Compatibility
No compatibility boundary is crossed: this is a patch or minor release on a stable major.
0 issues mention this version in stripe/stripe-node within 14 days of release. See them on GitHub
Check the official release notes below for behaviour changes before merging.
Release notes
Read the Stripe changelog on Changes.Watch or the package page on npm for this version’s features and fixes.
New in this release
- Multipart file uploads now use cryptographically secure boundaries.“* [#2831](https://github.com/stripe/stripe-node/pull/2831) Use cryptographically secure boundaries for multipart file uploads”
- API requestor code is hardened against malicious URLs.“* [#2829](https://github.com/stripe/stripe-node/pull/2829) Harden API requestor code against malicious URLs”
AI-extracted from the official release notes and checked against the quoted text. Read the source
Deprecations and deadlines
The maintainer has not deprecated this version on npm.