podexit

CocoaPods trunk goes read-only on December 2, 2026. Builds keep working, but pods published there never get another version. podexit reads Podfile.lock and shows, for each pod, whether it stops getting updates and whether it already ships a Swift package, for native iOS, Flutter and React Native/Expo projects.

npx @mcamdali/podexit
Copy

The npm package is @mcamdali/podexit; the command it installs is podexit.

Guides

• What changes on December 2 (and what doesn't)
• Native iOS: CocoaPods to Swift Package Manager
• Flutter apps and plugins
• React Native and Expo
• Firebase after version 12
• Pod authors: replacing pod trunk push

API

The command line is a thin layer over the package's exports, so the same analysis runs from JavaScript:

import { analyzeLockfile, buildReport, CachedFetcher, HttpFetcher, loadPublisherPolicy, render } from '@mcamdali/podexit';

const policy = loadPublisherPolicy();
const fetcher = new CachedFetcher(new HttpFetcher({ userAgent: 'my-tool' }), { directory: '.cache' });
const lockfile = await analyzeLockfile(text, 'ios/Podfile.lock', { fetcher, policy });
console.log(render(buildReport([lockfile], { policy, offline: false }), 'markdown'));
Copy

Start with analyzeLockfile, buildReport and render; the JSON report is described by Report. Its schemaVersion is 0 until the layout is declared stable in 1.0.

Source, issues and the changelog are on GitHub.