Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-25 06:20 UTC

wizzcomms / wizz-method

Método de agência orientado por IA, em PT-BR. Um maestro lê seu pedido e chama o agente certo. Fork independente do BMad Method.

JavaScript · HTMLCustom license★ 0 stars⑂ 0 forkssince Jun 2026View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

wizzcomms/wizz-method holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (84/100) and lowest on Community & Adoption (45/100). It was last updated 3 days ago. 2 contributors account for most of its recent work.

77
overall / 100
Good

Software 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.

77
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)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

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 66 is calibrated to 77 on the published index scale (record calibration 2026-08-02).

Ownership

Wizz! commsPersonal account
0 followers7 public repossince Nov 2025

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmwizz-method1.7.02,935185 days agoagileaiorchestratordevelopmentmethodologyagentswizzwizzcomms

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

84Excellent · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 1,496 commits in the last year
0/10OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year1,496
human_commit_share0.99
days_since_last_push3
active_weeks_last_year51
How it's scored
27/27Ships releases — 1 releases published
36/36Release recency — latest release 17 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count1
latest_release_tagassets-v1
releases_from_tagsno
days_since_latest_release17
mean_days_between_releases—

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

45Weak · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes
How it's scored
46.2/80Monthly downloads — 2,935 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageswizz-method
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,935
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?

61Moderate · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.8/22.5Commit distribution — top contributor authored 39% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 11 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled98
top_contributor_share0.386
How it's scored
0/42Issue resolution — no issues or no data
30/30PR acceptance — 1/1 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues0
closed_issues0
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
0/25Owner reach — 0 followers of wizzcomms
7.9/25Track record — 7 public repos, account ~0 yr old
Inputs used
followers0
owner_typeUser
is_verified—
owner_loginwizzcomms
public_repos7
account_age_days244
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 5 days ago
20/20Version history — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswizz-method
ecosystemsnpm
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://method.wizzcomms.com
10/10Repository description
10/10Topics — 10 topics
10/10Wiki
Inputs used
topicsagency, agile, ai, ai-agents, bmad, claude-code, cursor, llm, methodology, portugues
has_wikiyes
homepagehttps://method.wizzcomms.com
docs_sitehttps://method.wizzcomms.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 11 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
0/7.5Maintained — project was created within the last 90 days. Please review its contents carefully
0/5Packaging — no data
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages98
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:wizz-method@1.7.0 runtime dependency closure — what installing the published package pulls in — 98 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.

73Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, docs/reference/agents.md, src/skills-lib/supabase-postgres-best-practices/AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 97 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.98
agent_instruction_filesAGENTS.md, docs/reference/agents.md, src/skills-lib/supabase-postgres-best-practices/AGENTS.md
agent_instruction_max_bytes4,965
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 22 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.22
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
53.6/55Manageable file sizes — 4/157 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes190,536
source_files_sampled157
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — demos, examples
Inputs used
example_dirsdemos, examples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

0GitHub stars
98contributors
1,496commits, last 12 months
3days since last push
1releases
2bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.3 / 10
4.3aggregate

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).Scorecard v5.5.0 · 2026-07-25 06:20 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
npm@clack/core^1.3.1package.json
npm@clack/prompts^1.4.0package.json
npm@kayvan/markdown-tree-parser^1.6.1package.json
npmchalk^4.1.2package.json
npmcommander^14.0.0package.json
npmcsv-parse^6.1.0package.json
npmglob^11.0.3package.json
npmignore^7.0.5package.json
npmjs-yaml^4.3.0package.json
npmpicocolors^1.1.1package.json
npmsemver^7.6.3package.json
npmxml2js^0.6.2package.json
npmyaml^2.7.0package.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:wizz-method@1.7.0 pulls in 98 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.

The message is kept through sign-in.

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.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.