Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 01:39 UTC

i-Cell-Mobilsoft-Open-Source / ids-styles

This repository contains styles for i-Cell Design System UI Kits (currently Vue and Angular).

SCSSMIT★ 0 stars⑂ 0 forkssince Apr 2024View on GitHub ↗

i-Cell-Mobilsoft-Open-Source/ids-styles holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Vitality (90/100) and lowest on AI Readiness (29/100). It was last updated 5 days ago. 3 contributors account for most of its recent work.

62
overall / 100
Moderate

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.

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

Ownership

24 followers43 public repossince Apr 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@i-cell/ids-styles0.0.748858728 days ago

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recencylast push 5 days ago
19.4/36Commit cadence28/52 weeks with commits
18/18Commit volume106 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year106
human_commit_share1
days_since_last_push5
active_weeks_last_year28

Release discipline

100Exceptional
How it's scored
27/27Ships releases51 releases published
36/36Release recencylatest release 28 days ago
27/27Release cadencea release every ~16.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count51
latest_release_tag0.0.74
releases_from_tagsno
days_since_latest_release28
mean_days_between_releases16.2
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?

30At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
39.3/80Monthly downloads885 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@i-cell/ids-styles
dependents
ecosystemsnpm
total_downloads
monthly_downloads885
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?

81Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
17.8/22.5Commit distributiontop contributor authored 21% of commits
13.5/13.5Contributor breadth11 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor3
contributors_sampled11
top_contributor_share0.209
How it's scored
0/42Issue resolutionno issues or no data
29.4/30PR acceptance155/158 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 13/17 approved changesets -- score normalized to 7
Inputs used
merged_prs155
open_issues0
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio
closed_unmerged_prs3
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
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 domain
10.1/25Owner reach24 followers of i-Cell-Mobilsoft-Open-Source
24/25Track record43 public repos, account ~6 yr old
Inputs used
followers24
owner_typeOrganization
is_verifiedno
owner_logini-Cell-Mobilsoft-Open-Source
public_repos43
account_age_days2,334

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 28 days ago
20/20Version history87 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@i-cell/ids-styles
ecosystemsnpm
any_deprecatedno
min_days_since_publish28

Engineering Quality

Are baseline engineering and documentation practices in place?

30At Risk · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 13 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
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?

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 13 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 13/17 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities14 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories14
affected_packages5
assessed_packages173
unassessed_packages0
affected_by_severitycritical 1, high 3, moderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 173 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

29At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history87 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.87
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeSCSS without a type-check config
55/55Manageable file sizes0/3 source files over 60KB
Inputs used
primary_languageSCSS
largest_source_bytes4,101
source_files_sampled3
oversized_source_files0

Key facts

0GitHub stars
11contributors
106commits, last 12 months
5days since last push
51releases
3bus factor
0open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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-09-09 01:39 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal 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
0CI-Tests0 out of 13 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 13/17 approved changesets -- score normalized to 7
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities14 existing vulnerabilities detected
All dependencies 173

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

RegistryPackageVersionRelation
npm@gulpjs/messages1.1.0indirect
npm@gulpjs/to-absolute-glob4.0.0indirect
npm@i-cell/ids-tokens0.0.45indirect
npmansi-colors1.1.0indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmansi-wrap0.1.0indirect
npmanymatch3.1.3indirect
npmarr-diff4.0.0indirect
npmarr-union3.1.0indirect
npmarray-each1.0.1indirect
npmarray-slice1.1.0indirect
npmassign-symbols1.0.0indirect
npmasync-done2.0.0indirect
npmasync-settle2.0.0indirect
npmb4a1.6.6indirect
npmbach2.0.1indirect
npmbare-events2.4.2indirect
npmbase64-js1.5.1indirect
npmbinary-extensions2.3.0indirect
npmbl5.1.0indirect
npmbraces3.0.3indirect
npmbuffer6.0.3indirect
npmcamelcase-css2.0.1indirect
npmchalk4.1.2indirect
npmchokidar3.6.0indirect
npmcliui7.0.4indirect
npmclone2.1.2indirect
npmclone-stats1.0.0indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcommander12.1.0indirect
npmconvert-source-map2.0.0indirect
npmcopy-props4.0.0indirect
npmdetect-file1.0.0indirect
npmeach-props3.0.0indirect
npmemoji-regex8.0.0indirect
npmend-of-stream1.4.4indirect
npmescalade3.1.2indirect
npmexpand-tilde2.0.2indirect
npmextend3.0.2indirect
npmextend-shallow3.0.2indirect
npmfast-fifo1.3.2indirect
npmfast-levenshtein3.0.0indirect
npmfastest-levenshtein1.0.16indirect
npmfastq1.17.1indirect
npmfill-range7.1.1indirect
npmfindup-sync5.0.0indirect
npmfined2.0.0indirect
npmflagged-respawn2.0.0indirect
npmfor-in1.0.2indirect
npmfor-own1.0.0indirect
npmfs-mkdirp-stream2.0.1indirect
npmfsevents2.3.3indirect
npmfunction-bind1.1.2indirect
npmget-caller-file2.0.5indirect
npmglob-parent5.1.2indirect
npmglob-parent6.0.2indirect
npmglob-stream8.0.2indirect
npmglob-watcher6.0.0indirect
npmglobal-modules1.0.0indirect
npmglobal-prefix1.0.2indirect
npmglogg2.2.0indirect
npmgraceful-fs4.2.11indirect
npmgulp5.0.0indirect
npmgulp-cli3.0.0indirect
npmgulp-prettier6.0.0indirect
npmgulp-rename2.0.0indirect
npmgulp-sass5.1.0indirect
npmgulplog2.2.0indirect
npmhas-flag4.0.0indirect
npmhasown2.0.2indirect
npmhomedir-polyfill1.0.3indirect
npmiconv-lite0.6.3indirect
npmieee7541.2.1indirect
npmimmutable4.3.6indirect
npminherits2.0.4indirect
npmini1.3.8indirect
npminterpret3.1.1indirect
npmis-absolute1.0.0indirect
npmis-binary-path2.1.0indirect
npmis-core-module2.14.0indirect
npmis-extendable1.0.1indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-negated-glob1.0.0indirect
npmis-number7.0.0indirect
npmis-plain-object2.0.4indirect
npmis-plain-object5.0.0indirect
npmis-relative1.0.0indirect
npmis-unc-path1.0.0indirect
npmis-valid-glob1.0.0indirect
npmis-windows1.0.2indirect
npmisexe2.0.0indirect
npmisobject3.0.1indirect
npmlast-run2.0.0indirect
npmlead4.0.0indirect
npmliftoff5.0.0indirect
npmlodash.clonedeep4.5.0indirect
npmmap-cache0.2.2indirect
npmmicromatch4.0.7indirect
npmmute-stdout2.0.0indirect
npmnanoid3.3.7indirect
npmnormalize-path3.0.0indirect
npmnow-and-later3.0.0indirect
npmobject-inspect1.13.2indirect
npmobject.defaults1.1.0indirect
npmobject.pick1.3.0indirect
npmonce1.4.0indirect
npmparse-filepath1.0.2indirect
npmparse-passwd1.0.0indirect
npmpath-parse1.0.7indirect
npmpath-root0.1.1indirect
npmpath-root-regex0.1.2indirect
npmpicocolors1.0.1indirect
npmpicomatch2.3.1indirect
npmplugin-error1.0.1indirect
npmplugin-error2.0.1indirect
npmpostcss8.4.38indirect
npmpostcss-js4.0.1indirect
npmprettier3.3.2indirect
npmqueue-tick1.0.1indirect
npmreadable-stream3.6.2indirect
npmreaddirp3.6.0indirect
npmrechoir0.8.0indirect
npmremove-trailing-separator1.1.0indirect
npmreplace-ext2.0.0indirect
npmreplace-homedir2.0.0indirect
npmrequire-directory2.1.1indirect
npmresolve1.22.8indirect
npmresolve-dir1.0.1indirect
npmresolve-options2.0.0indirect
npmreusify1.0.4indirect
npmsafe-buffer5.2.1indirect
npmsafer-buffer2.1.2indirect
npmsass1.77.6indirect
npmsemver6.3.1indirect
npmsemver-greatest-satisfied-range2.0.0indirect
npmsource-map0.5.7indirect
npmsource-map-js1.2.0indirect
npmsparkles2.1.0indirect
npmstream-composer1.0.2indirect
npmstream-exhaust1.0.2indirect
npmstreamx2.18.0indirect
npmstring-width4.2.3indirect
npmstring_decoder1.3.0indirect
npmstrip-ansi6.0.1indirect
npmsupports-color7.2.0indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmsver1.8.4indirect
npmteex1.0.1indirect
npmtext-decoder1.1.0indirect
npmthrough24.0.2indirect
npmto-regex-range5.0.1indirect
npmto-through3.0.0indirect
npmunc-path-regex0.1.2indirect
npmundertaker2.0.0indirect
npmundertaker-registry2.0.0indirect
npmutil-deprecate1.0.2indirect
npmv8flags4.0.1indirect
npmvalue-or-function4.0.0indirect
npmvinyl3.0.0indirect
npmvinyl-contents2.0.0indirect
npmvinyl-fs4.0.0indirect
npmvinyl-sourcemap2.0.0indirect
npmvinyl-sourcemaps-apply0.2.1indirect
npmwhich1.3.1indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyargs16.2.0indirect
npmyargs-parser20.2.9indirect
Dependency advisories 5

This repository publishes no package the index resolves, so its own dependency graph was assessed — 173 packages, which also include development and test pins that never ship: 5 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
immutable4.3.6indirectcritical35.1.8
nanoid3.3.7indirecthigh45.1.16
picomatch2.3.1indirecthigh24.0.4
postcss8.4.38indirecthigh48.5.23
micromatch4.0.7indirectmoderate14.0.8

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

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