Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-19 07:44 UTC

DCODE-GROUP / laravel-activity-log

Dcodegroup Activity Log

JavaScriptNo license detected★ 4 stars⑂ 0 forkssince Jan 2024View on GitHub ↗
KindLibraryNetwork servicehow this is determined

DCODE-GROUP/laravel-activity-log holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Vitality (84/100) and lowest on Community & Adoption (27/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

DCODE GROUPOrganization
10 followers41 public repossince Feb 2015

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistdcodegroup/activity-log3.0.22,2427517 days agodatalaravelactivity-logscommunication-logs

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 recencylast push 0 days ago
11.1/36Commit cadence16/52 weeks with commits
16.3/18Commit volume65 commits in the last year
10/10OpenSSF Scorecard: Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year65
human_commit_share
days_since_last_push0
active_weeks_last_year16

Release discipline

100Exceptional
How it's scored
27/27Ships releases76 releases published
36/36Release recencylatest release 16 days ago
27/27Release cadencea release every ~22.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count76
latest_release_tag3.0.2
releases_from_tagsno
days_since_latest_release16
mean_days_between_releases22.8
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?

27At Risk · 17% of overall
How it's scored
7.7/60Stars4 stars
0/25Forks0 forks
3.3/15Watchers5 watchers
Inputs used
forks0
stars4
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
44.7/80Monthly downloads2,242 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagesdcodegroup/activity-log
dependents0
ecosystemspackagist
total_downloads131,939
monthly_downloads2,242
unverified_packages_excluded

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

73Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.2/22.5Commit distributiontop contributor authored 55% of commits
13.5/13.5Contributor breadth17 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.546
How it's scored
0/42Issue resolutionno issues or no data
29/30PR acceptance88/91 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 7/9 approved changesets -- score normalized to 7
Inputs used
merged_prs88
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs3
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
7.5/25Owner reach10 followers of DCODE-GROUP
23.8/25Track record41 public repos, account ~11 yr old
Inputs used
followers10
owner_typeOrganization
is_verified
owner_loginDCODE-GROUP
public_repos41
account_age_days4,171
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 17 days ago
20/20Version history75 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdcodegroup/activity-log
ecosystemspackagist
any_deprecatedno
min_days_since_publish17

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests7 out of 8 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2/2.5CI-Tests7 out of 8 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 7/9 approved changesets -- score normalized to 7
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.js
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
54.1/55Manageable file sizes1/58 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes713,464
source_files_sampled58
oversized_source_files1

Key facts

4GitHub stars
17contributors
65commits, last 12 months
0days since last push
76releases
1bus factor
0open issues
npm, Packagistpackage ecosystems

More detail

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-19 07:43 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests7 out of 8 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 7/9 approved changesets -- score normalized to 7
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
Packagistcoduo/php-to-string^3.2composer.json
Packagistlaravel/framework^11.0|^12.0|^13.0composer.json
Packagistnesbot/carbon^2.72|^3.0composer.json
Packagistspatie/laravel-query-builder^5.7|^6.0|^7.0composer.json
npmlaravel-vue-i18n^2.7.6package.json
npmvue-i18n^9.14.4package.json
All dependencies 49

Full resolved dependency set from the GitHub dependency graph: 6 direct and 43 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npmlaravel-vue-i18n^2.7.6direct
npmvue-i18n^9.14.4direct
Packagistcoduo/php-to-stringdirect
Packagistlaravel/frameworkdirect
Packagistnesbot/carbondirect
Packagistspatie/laravel-query-builderdirect
npm@babel/eslint-parser^7.23.0indirect
npm@dcodegroup/vue-mention^0.0.2indirect
npm@heroicons/vue^2.1.1indirect
npm@typescript-eslint/eslint-plugin^7.1.1indirect
npm@vitejs/plugin-vue^6.0.0indirect
npm@vue/compiler-sfc^3.2.33indirect
npmautoprefixer10.4.5indirect
npmaxios1.13.6indirect
npmconcurrently^9.2.0indirect
npmeslint^8.57.0indirect
npmeslint-config-prettier^9.1.0indirect
npmeslint-config-standard^17.1.0indirect
npmeslint-friendly-formatter^4.0.1indirect
npmeslint-plugin-flow^2.29.1indirect
npmeslint-plugin-html^8.0.0indirect
npmeslint-plugin-jsx^0.1.0indirect
npmeslint-plugin-jsx-a11y^6.5.1indirect
npmeslint-plugin-prettier^5.1.3indirect
npmeslint-plugin-prettier-vue^5.0.0indirect
npmeslint-plugin-promise^6.1.1indirect
npmeslint-plugin-vue^9.22.0indirect
npmfloating-vue^5.2.2indirect
npmmitt^3.0.1indirect
npmnpm-run-all^4.1.5indirect
npmpostcss^8.5.6indirect
npmresolve-url-loader^4.0.0indirect
npmsass^1.39.0indirect
npmsass-loader^12.1.0indirect
npmtailwindcss^3.4.1indirect
npmvite^6.0.0indirect
npmvite-plugin-laravel-translations^0.2.2indirect
npmvue^3.2.37indirect
npmvue-loader^16.8.3indirect
npmvue-markdown-render^2.1.1indirect
npmvue-router^3.0.1indirect
Packagistergebnis/composer-normalizeindirect
Packagistlarastan/larastanindirect
Packagistlaravel/pintindirect
Packagistorchestra/testbenchindirect
Packagistphpindirect
Packagistphpstan/phpstan-deprecation-rulesindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistspatie/laravel-log-dumperindirect
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.14.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPackagist.