npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

cf-progress

v1.0.0

Published

Suivi de progression pour projets Claude-Flow avec double persistance (mémoire + document)

Readme

CF-Progress

Outil de suivi de progression pour projets Claude-Flow avec double persistance :

  1. Mémoire Claude-Flow (.swarm/memory.db) - Recherche sémantique
  2. Document lisible (.claude/PROJECT_PROGRESS.md) - Historique humain

Installation

# Installation globale
npm install -g cf-progress

# Ou installation locale dans un projet
npm install cf-progress

Utilisation

Initialiser un projet

cd mon-projet
cf-progress init "Mon Projet" "mon_namespace"

# Ou avec le nom du dossier comme défaut
cf-progress init

Sauvegarder une phase

Après chaque phase SPARC :

cf-progress save specification "API REST définie avec 5 endpoints" "JWT, PostgreSQL"
cf-progress save architecture "Microservices avec Docker" "Redis, RabbitMQ"
cf-progress save implementation "Backend terminé, 45 tests"
cf-progress save testing "Couverture 92%, tests E2E passent"
cf-progress save completion "Déployé en production" "CI/CD GitHub Actions"

Voir la progression

cf-progress show

Lister les phases mémorisées

cf-progress list

Phases SPARC suggérées

| Phase | Description | |-------|-------------| | specification | Analyse des besoins | | pseudocode | Algorithmes en pseudo-code | | architecture | Design système | | implementation | Développement | | testing | Tests et validation | | completion | Finalisation |

Structure créée

mon-projet/
├── .claude/
│   ├── PROJECT_PROGRESS.md    ← Document de suivi lisible
│   └── progress-config.json   ← Configuration du projet
└── .swarm/
    └── memory.db              ← Mémoire Claude-Flow (si disponible)

Récupération du contexte

# Voir le document
cf-progress show

# Rechercher dans la mémoire Claude-Flow
npx claude-flow@alpha memory query "architecture" --namespace mon_projet

# Lister toutes les entrées
npx claude-flow@alpha memory list --namespace mon_projet

Exemple de workflow complet

# 1. Créer et initialiser le projet
mkdir mon-api && cd mon-api
git init
cf-progress init "Mon API REST" "api_v1"

# 2. Phase Spécification
# ... travailler sur les specs ...
cf-progress save specification "5 endpoints définis: users, auth, products" "REST, JWT RS256"

# 3. Phase Architecture
# ... designer l'architecture ...
cf-progress save architecture "3-tiers: API Gateway, Services, DB" "PostgreSQL, Redis, Docker"

# 4. Phase Implémentation
# ... coder ...
cf-progress save implementation "Backend complet, 45 tests unitaires" "Express, Prisma"

# 5. Phase Tests
# ... tester ...
cf-progress save testing "92% coverage, tests E2E OK" "Jest, Supertest"

# 6. Phase Completion
# ... déployer ...
cf-progress save completion "Déployé sur AWS ECS" "Terraform, GitHub Actions"

# 7. Voir le résultat
cf-progress show

Licence

MIT