🔍 Scanning your project...

Detected:

✓ React Native 0.82
✓ Expo SDK 54
✓ TypeScript 7
✓ Drizzle ORM

──────────────

🔥 5 things happened this week

1. TypeScript 7

You should care because:
Your project has 1,342 TypeScript files.
This release improves incremental builds.

Sources:
• Announcing TypeScript 7
  https://devblogs.microsoft.com/typescript/...

Recommendation:
Worth testing.

──────────────

Features

• Detects your stack from package.json (TypeScript, Expo, React Native, Next.js, Drizzle, and more)
• Looks up latest versions on npm
• Uses OpenAI web search for major package/framework news
• Source links on every item (blogs, changelogs, GitHub Releases)
• Saves your OpenAI API key locally (~/.package-radar/) and protects project .gitignore

Package Radar focuses on major news — not security audits or CVE noise.

Requirements

• Node.js 20 or later
• An OpenAI API key with access to the Responses API + web search

Installation

Using npm:

npm install -g package-radar

Using yarn:

yarn global add package-radar

Or run once without installing:

npx package-radar

Usage

From any Node project directory:

package-radar

First run prompts for your OpenAI API key (saved to ~/.package-radar/config.json). You can also set OPENAI_API_KEY in the environment.

package-radar config          # save / update API key
package-radar config --show   # check if a key is configured
package-radar config --clear  # remove saved key
package-radar --help

What happens on each run

1. Scan — nearest package.json, known frameworks, source file counts
2. Registry — latest versions on npm for detected packages
3. News — OpenAI web search for major announcements
4. Report — why it matters, recommendation, and source URLs
5. Safety — appends .package-radar/ to the project .gitignore if missing

Config & environment

| Variable / path | Required | Description | | --- | --- | --- | | OPENAI_API_KEY | Yes* | Overrides the saved key when set. Get a key. | | OPENAI_MODEL | No | Model name (default: gpt-4.1-mini). | | ~/.package-radar/config.json | — | Where the API key is stored after package-radar config. |

*Required either as env var or via package-radar config.

Local development

git clone https://github.com/watadarkstar/code-radar.git
cd code-radar
yarn install
yarn start          # run via tsx
yarn build          # emit dist/
yarn typecheck

| Script | Description | | --- | --- | | yarn start / yarn radar / yarn dev | Run the CLI from source | | yarn build | Build with tsup → dist/ | | yarn typecheck | tsc --noEmit | | yarn clean | Remove dist/ | | yarn release:dry | Dry-run a release | | yarn release | Version, tag, GitHub release, publish to npm |

License

MIT

Author

Feel free to ask me questions on Twitter @icookandcode!

Contributors

Submit a PR to contribute :)

Release

We use release-it to version, tag, create a GitHub release, and publish to npm.

Prerequisites:

1. Logged into npm: npm login
2. GH_TOKEN (or GITHUB_TOKEN) with repo access if you want GitHub releases
3. Clean git working tree on the default branch

Then:

yarn run release:dry
yarn run release

release:dry prints what would happen without publishing. release bumps the version, runs typecheck + build, commits/tags, creates a GitHub release, and publishes package-radar to the npm registry.

Stay ahead of your stack.

⭐ Star this repo • 💬 Contact Adrian

Built with ❤️ by Adrian

Keywords: cli, package-radar, package news, dependencies, changelog, npm, openai, typescript, developer-tools