Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-26 10:31 UTC

iamport / iamport-rest-client-nodejs

NodeJS사용자를 위한 아임포트 REST API 연동 모듈입니다.

JavaScriptMIT★ 66 stars⑂ 21 forkssince Nov 2015archivedView on GitHub ↗

iamport/iamport-rest-client-nodejs holds a health index of 16 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (75/100) and lowest on Vitality (16/100). The repository is archived, so no further maintenance is expected.

16
overall / 100
Critical

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.

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

Ownership

PortOneOrganization
114 followers52 public repossince Mar 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmiamport0.4.09,68110205 days agoiamportrestsdkiamport-node-sdk

Metrics by category

Vitality

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

16Critical · 21% of overall
How it's scored
3.6/36Push recency — last push 205 days ago
0.7/36Commit cadence — 1/52 weeks with commits
5.4/18Commit volume — 3 commits in the last year
0/10OpenSSF Scorecard: Maintained — project is archived
Inputs used
commits_last_year3
human_commit_share1
days_since_last_push205
active_weeks_last_year1
How it's scored
16.2/27Ships releases — 3 version tags (no GitHub releases)
0/36Release recency — latest release 1,754 days ago
5.4/27Release cadence — a release every ~1,096.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv0.3.6
releases_from_tagsyes
days_since_latest_release1,754
mean_days_between_releases1,096.3
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?

53Moderate · 17% of overall
How it's scored
29.4/60Stars — 66 stars
10.8/25Forks — 21 forks
7.2/15Watchers — 21 watchers
Inputs used
forks21
stars66
watchers21
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, travis-ci.org
has_pull_request_templateno
How it's scored
53.1/80Monthly downloads — 9,681 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesiamport
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads9,681
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?

75Good · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
17.9/22.5Commit distribution — top contributor authored 20% of commits
13.5/13.5Contributor breadth — 15 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled15
top_contributor_share0.203
How it's scored
24/42Issue resolution — 57% of issues closed
28/30PR acceptance — 14/15 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 7/22 approved changesets -- score normalized to 3
Inputs used
merged_prs14
open_issues3
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.571
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
14.8/25Owner reach — 114 followers of iamport
24.6/25Track record — 52 public repos, account ~11 yr old
Inputs used
followers114
owner_typeOrganization
is_verifiedno
owner_loginiamport
public_repos52
account_age_days4,216
How it's scored
25/25Published & resolvable — 1 package(s) on npm
26/35Publish recency — latest publish 205 days ago
20/20Version history — 10 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesiamport
ecosystemsnpm
any_deprecatedno
min_days_since_publish205

Engineering Quality

Are baseline engineering and documentation practices in place?

40Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 8 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://iamport.kr/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttp://iamport.kr/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

26At Risk · 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 8 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
2.2/7.5Code-Review — Found 7/22 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 4 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — project is archived
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 20 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.1
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
17.9/35Direct dependencies free of known advisories — 1 affected: request 2.88.2 (moderate 6.1)
6.7/25Indirect dependencies free of known advisories — 4 affected: form-data 2.3.3 (high 7.5), uuid 3.4.0 (high 7.5), qs 6.5.5 (moderate 5.3), +1 more
21.9/40No advisories left outstanding — 5 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,289 days ago
Inputs used
sourceosv
advisories7
affected_packages5
assessed_packages49
unassessed_packages0
affected_by_severityhigh 2, moderate 3
direct_affected_packages1
Matched the npm:iamport@0.4.0 runtime dependency closure — what installing the published package pulls in — 49 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.

35Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
15.6/40Legible commit history — 22 of 75 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.293
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 75
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/40 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes21,670
source_files_sampled40
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — openapi.json
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filesopenapi.json
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

66GitHub stars
15contributors
3commits, last 12 months
205days since last push
3releases
3bus factor
3open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 21 ⇿
0Stars
21Forks
3Releases

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.

048121620242122015-122019-082023-04
Major 0Minor 1Patch 2

Each point covers 7 days.

OpenSSF Scorecard 2.1 / 10
2.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-26 10:31 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 7/22 approved changesets -- score normalized to 3
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
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
0Vulnerabilities20 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmbluebird^3.4.1package.json
npmlodash^4.17.2package.json
npmrequest^2.68.0package.json
All dependencies 89

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

RegistryPackageVersionRelation
npmbluebird3.7.2direct
npmlodash4.17.23direct
npmrequest2.88.2direct
npmajv6.14.0indirect
npmasn10.2.6indirect
npmassert-plus1.0.0indirect
npmassertion-error1.1.0indirect
npmasynckit0.4.0indirect
npmaws-sign20.7.0indirect
npmaws41.13.2indirect
npmbalanced-match1.0.2indirect
npmbcrypt-pbkdf1.0.2indirect
npmbrace-expansion1.1.12indirect
npmbrowser-stdout1.3.0indirect
npmcaseless0.12.0indirect
npmchai3.5.0indirect
npmcombined-stream1.0.8indirect
npmcommander2.9.0indirect
npmconcat-map0.0.1indirect
npmcore-util-is1.0.2indirect
npmdashdash1.14.1indirect
npmdebug2.6.8indirect
npmdeep-eql0.1.3indirect
npmdelayed-stream1.0.0indirect
npmdiff3.2.0indirect
npmecc-jsbn0.1.2indirect
npmescape-string-regexp1.0.5indirect
npmextend3.0.2indirect
npmextsprintf1.3.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmforever-agent0.6.1indirect
npmform-data2.3.3indirect
npmfs.realpath1.0.0indirect
npmgetpass0.1.7indirect
npmglob7.1.1indirect
npmgraceful-readlink1.0.1indirect
npmgrowl1.9.2indirect
npmhar-schema2.0.0indirect
npmhar-validator5.1.5indirect
npmhas-flag1.0.0indirect
npmhe1.1.1indirect
npmhttp-signature1.2.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-typedarray1.0.0indirect
npmisstream0.1.2indirect
npmjsbn0.1.1indirect
npmjson-schema0.4.0indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stringify-safe5.0.1indirect
npmjson33.3.2indirect
npmjsprim1.4.2indirect
npmlodash._baseassign3.2.0indirect
npmlodash._basecopy3.0.1indirect
npmlodash._basecreate3.0.3indirect
npmlodash._getnative3.9.1indirect
npmlodash._isiterateecall3.0.9indirect
npmlodash.create3.1.1indirect
npmlodash.isarguments3.1.0indirect
npmlodash.isarray3.0.4indirect
npmlodash.keys3.1.2indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmminimatch3.1.5indirect
npmminimist0.0.8indirect
npmmkdirp0.5.1indirect
npmmocha3.5.3indirect
npmms2.0.0indirect
npmoauth-sign0.9.0indirect
npmonce1.4.0indirect
npmpath-is-absolute1.0.1indirect
npmperformance-now2.1.0indirect
npmpsl1.15.0indirect
npmpunycode2.3.1indirect
npmqs6.5.5indirect
npmsafe-buffer5.2.1indirect
npmsafer-buffer2.1.2indirect
npmsshpk1.18.0indirect
npmsupports-color3.1.2indirect
npmtough-cookie2.5.0indirect
npmtunnel-agent0.6.0indirect
npmtweetnacl0.14.5indirect
npmtype-detect0.1.1indirect
npmtype-detect1.0.0indirect
npmuri-js4.4.1indirect
npmuuid3.4.0indirect
npmverror1.10.0indirect
npmwrappy1.0.2indirect
Dependency advisories 5

Installing npm:iamport@0.4.0 pulls in 49 packages, direct and transitive: 5 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
form-data2.3.3indirecthigh24.0.6
uuid3.4.0indirecthigh113.0.1
request2.88.2directmoderate13.0.0
qs6.5.5indirectmoderate26.16.0
tough-cookie2.5.0indirectmoderate14.1.3

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 statistics — npm.