Public recordExcellent
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 19:58 UTC
armitage-labs / creem
Creem repo for all integrations
armitage-labs/creem holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (98/100) and lowest on Security (62/100). It was last updated today. 2 contributors account for most of its recent work.
89
overall / 100Software health index
Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.
89
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
Score profile
Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.
The weighted overall 75 is calibrated to 89 on the published index scale (record calibration 2026-08-02).
Ownership
Armitage LabsOrganization
41 followers16 public repossince Feb 2024
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| npm | @creem_io/cli | 0.3.0 | 240 | 4 | 2 days ago | creemclipaymentssaassubscriptions |
| npm | creem | 1.7.0 | 117,380 | 38 | 2 days ago | — |
| npm | creem_io⚠ This package is deprecated. Please use the 'creem' package instead: npm install creem | 1.1.0 | 2,485 | 3 | 184 days ago | creempaymentssubscriptionssdkapitypescriptjavascriptcheckoutwebhookslicensesbillingsaas |
| npm | @creem_io/webhook-types | 1.0.1 | 11,189 | 2 | 6 days ago | creemwebhookstypestypescript |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
98
Development activity
96Exceptional
How it's scored
| 36/36 | Push recency — last push 0 days ago |
| 32.5/36 | Commit cadence — 47/52 weeks with commits |
| 18/18 | Commit volume — 438 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 438 |
| human_commit_share | 0.75 |
| days_since_last_push | 0 |
| active_weeks_last_year | 47 |
Release discipline
100Exceptional
How it's scored
| 27/27 | Ships releases — 40 releases published |
| 36/36 | Release recency — latest release 1 days ago |
| 27/27 | Release cadence — a release every ~0.6 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 40 |
| latest_release_tag | @creem_io/nextjs@0.5.7 |
| releases_from_tags | no |
| days_since_latest_release | 1 |
| mean_days_between_releases | 0.6 |
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
65
Popularity & adoption
30At Risk
How it's scored
| 22.4/60 | Stars — 25 stars |
| 7.5/25 | Forks — 9 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 9 |
| stars | 25 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
92Excellent
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 18/18 | CONTRIBUTING guide |
| 13.5/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 6.3/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 3 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | shields.io |
| has_pull_request_template | yes |
Ecosystem adoption (downloads)
85Excellent
How it's scored
| 68.2/80 | Monthly downloads — 131,294 downloads/month across npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | @creem_io/cli, creem, creem_io, @creem_io/webhook-types |
| dependents | — |
| ecosystems | npm |
| total_downloads | — |
| monthly_downloads | 131,294 |
| unverified_packages_excluded | — |
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
68
Maintainer resilience (bus factor)
62Moderate
How it's scored
| 25.2/54 | Bus factor — 2 contributor(s) cover half of all commits |
| 13.5/22.5 | Commit distribution — top contributor authored 40% of commits |
| 13.5/13.5 | Contributor breadth — 26 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations |
Inputs used
| bus_factor | 2 |
| contributors_sampled | 26 |
| top_contributor_share | 0.401 |
How it's scored
| 23.6/42 | Issue resolution — 56% of issues closed |
| 26.2/30 | PR acceptance — 168/192 decided PRs merged |
| 13/13 | Newcomer PR acceptance — 10/10 first-time contributors' PRs merged in 30d |
| 13.5/15 | OpenSSF Scorecard: Code-Review — Found 18/20 approved changesets -- score normalized to 9 |
Inputs used
| merged_prs | 168 |
| open_issues | 7 |
| closed_issues | 9 |
| prs_merged_7d | 9 |
| prs_decided_7d | 9 |
| prs_merged_30d | 34 |
| prs_decided_30d | 34 |
| issue_closed_ratio | 0.562 |
| closed_unmerged_prs | 24 |
| first_time_authors_30d | 4 |
| first_time_prs_merged_30d | 10 |
| first_time_prs_decided_30d | 10 |
Ownership & stewardship
56Moderate
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain |
| 11.7/25 | Owner reach — 41 followers of armitage-labs |
| 14.1/25 | Track record — 16 public repos, account ~2 yr old |
Inputs used
| followers | 41 |
| owner_type | Organization |
| is_verified | no |
| owner_login | armitage-labs |
| public_repos | 16 |
| account_age_days | 931 |
Package maintenance
80Excellent
How it's scored
| 25/25 | Published & resolvable — 4 package(s) on npm |
| 35/35 | Publish recency — latest publish 2 days ago |
| 20/20 | Version history — 38 published versions |
| 0/20 | Not deprecated — creem_io: This package is deprecated. Please use the 'creem' package instead: npm install creem |
Inputs used
| packages | @creem_io/cli, creem, creem_io, @creem_io/webhook-types |
| ecosystems | npm |
| any_deprecated | yes |
| min_days_since_publish | 2 |
Engineering Quality
Are baseline engineering and documentation practices in place?
76
Engineering practices
90Excellent
How it's scored
| 24/24 | CI workflows — 9 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — .eslintrc.json, eslint.config.js, eslint.config.mjs |
| 0/9.6 | Pre-commit hooks |
| 6.4/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | yes |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
55Moderate
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://creem.io |
| 10/10 | Repository description |
| 0/10 | Topics |
| 0/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | no |
| homepage | — |
| docs_site | https://creem.io |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
62
Security posture
52Moderate
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 2.5/2.5 | CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 6.8/7.5 | Code-Review — Found 18/20 approved changesets -- score normalized to 9 |
| 2.5/2.5 | Contributors — project has 5 contributing companies or organizations |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 5/5 | Security-Policy — security policy file detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 0/7.5 | Vulnerabilities — 233 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 15 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 3 |
| scorecard_aggregate | 5.2 |
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
Dependency advisories
100Exceptional
How it's scored
| 35/35 | Direct dependencies free of known advisories — no direct dependency carries a known advisory |
| 25/25 | Indirect dependencies free of known advisories — no indirect dependency carries a known advisory |
| 0/40 | No advisories left outstanding — no advisory carries a publication date |
Inputs used
| source | osv |
| advisories | 0 |
| affected_packages | 0 |
| assessed_packages | 96 |
| unassessed_packages | 0 |
| affected_by_severity | none |
| direct_affected_packages | 0 |
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:creem@1.7.0 runtime dependency closure — what installing the published package pulls in — 96 packages. Reachability is not analyzed.
AI Readiness
How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.
86
Agent context & guidance
100Exceptional
How it's scored
| 45/45 | Agent instructions — AGENTS.md, packages/cli/AGENTS.md, packages/docs/CLAUDE.md, packages/integrations/convex/AGENTS.md |
| 15/15 | Machine-readable docs (llms.txt) — llms.txt present |
| 40/40 | Legible commit history — 75 of 75 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | yes |
| llms_txt_url | — |
| legible_history_share | 1 |
| agent_instruction_files | AGENTS.md, packages/cli/AGENTS.md, packages/docs/CLAUDE.md, packages/integrations/convex/AGENTS.md |
| agent_instruction_max_bytes | 15,789 |
Verify loop (build / test / typecheck)
64Moderate
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — .eslintrc.json, eslint.config.js, eslint.config.mjs |
| 11/11 | Static type checking — packages/cli/tsconfig.json, packages/creem-io/tsconfig.json, packages/examples/safe-metered-ai-generator/tsconfig.json, packages/integrations/better-auth/examples/nextjs/tsconfig.json, packages/integrations/better-auth/test/nextjs-app/tsconfig.json, packages/integrations/better-auth/tsconfig.json, packages/integrations/convex/convex/tsconfig.json, packages/integrations/convex/example-react/tsconfig.json, packages/integrations/convex/example-svelte/tsconfig.json, packages/integrations/convex/tsconfig.json, packages/integrations/framer/tsconfig.json, packages/integrations/nextjs/example/tsconfig.json, packages/integrations/nextjs/tsconfig.json, packages/integrations/strapi/admin/tsconfig.json, packages/integrations/strapi/server/tsconfig.json, packages/sdk/tsconfig.json, packages/ui/embed/tsconfig.json, packages/ui/react/tsconfig.json, packages/ui/svelte/tsconfig.json, packages/ui/vue/tsconfig.json, packages/webhook-types/tsconfig.json |
| 10/10 | Reproducible environment — devcontainer, lockfile |
| 10/10 | Demonstrated agent practice — 10 of the last 100 commits agent-authored or agent-credited |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | package-lock.json, pnpm-lock.yaml, yarn.lock |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | yes |
| has_linter_config | yes |
| typecheck_configs | packages/cli/tsconfig.json, packages/creem-io/tsconfig.json, packages/examples/safe-metered-ai-generator/tsconfig.json, packages/integrations/better-auth/examples/nextjs/tsconfig.json, packages/integrations/better-auth/test/nextjs-app/tsconfig.json, packages/integrations/better-auth/tsconfig.json, packages/integrations/convex/convex/tsconfig.json, packages/integrations/convex/example-react/tsconfig.json, packages/integrations/convex/example-svelte/tsconfig.json, packages/integrations/convex/tsconfig.json, packages/integrations/framer/tsconfig.json, packages/integrations/nextjs/example/tsconfig.json, packages/integrations/nextjs/tsconfig.json, packages/integrations/strapi/admin/tsconfig.json, packages/integrations/strapi/server/tsconfig.json, packages/sdk/tsconfig.json, packages/ui/embed/tsconfig.json, packages/ui/react/tsconfig.json, packages/ui/svelte/tsconfig.json, packages/ui/vue/tsconfig.json, packages/webhook-types/tsconfig.json |
| agent_commit_share | 0.1 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — TypeScript (statically typed) |
| 54.8/55 | Manageable file sizes — 3/828 source files over 60KB |
Inputs used
| primary_language | TypeScript |
| largest_source_bytes | 88,778 |
| source_files_sampled | 828 |
| oversized_source_files | 3 |
Machine-readable interfaces
100Exceptional
How it's scored
| 40/40 | API schema (OpenAPI/GraphQL/proto) — packages/docs/api-reference/openapi.json, packages/sdk/openapi.json |
| 20/20 | MCP server |
| 40/40 | Runnable examples — example, examples |
Inputs used
| example_dirs | example, examples |
| has_mcp_signal | yes |
| api_schema_files | packages/docs/api-reference/openapi.json, packages/sdk/openapi.json |
| interfaces_expected_of | — |
Key facts
25GitHub stars
26contributors
438commits, last 12 months
0days since last push
40releases
2bus factor
7open issues
npmpackage ecosystems
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
More detail
Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
21Releases
When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.
Major 0Minor 0Patch 0
OpenSSF Scorecard 5.2 / 10
5.2aggregate
Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| 10 | CI-Tests | 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 9 | Code-Review | Found 18/20 approved changesets -- score normalized to 9 |
| 10 | Contributors | project has 5 contributing companies or organizations |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 10 | Security-Policy | security policy file detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 0 | Vulnerabilities | 233 existing vulnerabilities detected |
Direct dependencies 9
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | @inquirer/prompts | ^7.5.1 | packages/cli/package.json |
| npm | chalk | ^4.1.2 | packages/cli/package.json |
| npm | cli-table3 | ^0.6.5 | packages/cli/package.json |
| npm | commander | ^12.1.0 | packages/cli/package.json |
| npm | creem | workspace:* | packages/cli/package.json |
| npm | ora | ^5.4.1 | packages/cli/package.json |
| npm | @modelcontextprotocol/sdk | ^1.26.0 | packages/sdk/package.json |
| npm | jsonpath-rfc9535 | 1.1.0 | packages/sdk/package.json |
| npm | zod | ^3.25.0 || ^4.0.0 | packages/sdk/package.json |
All dependencies not collected
The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
Dependency advisories 0
Installing npm:creem@1.7.0 pulls in 96 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.
No known advisories affect the assessed dependencies.
An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.
Raw JSON report machine-readable
Feedback
Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.
Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.
Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — npm.