RepoPilot

stevemao / left-pad

Search stevemao/left-pad

GitHub

Repository health

Security advisories, maintenance activity, dependencies and license for stevemao/left-pad, with what was checked and what was not.

Security

0
Critical
0 direct
0
High
0 direct
0
Moderate
0
Low

3 dependencies checked (3 direct), npm, via deps.dev. Findings apply only to the packages and versions checked.

OpenSSF Scorecard · 3.9/10

Checks sorted from strongest to weakest.

  • Binary-Artifactsno binaries found in the repo10/10
  • Fuzzingproject is fuzzed10/10
  • Licenselicense file detected10/10
  • Code-ReviewFound 12/19 approved changesets -- score normalized to 66/10
  • Maintainedproject is archived0/10
  • CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected0/10
  • Security-Policysecurity policy file not detected0/10
  • Branch-Protectionbranch protection not enabled on development/release branches0/10
  • SASTSAST tool is not run on all commits -- score normalized to 00/10
  • Dangerous-Workflowno workflows foundnot scored
  • Packagingpackaging workflow not detectednot scored
  • Pinned-Dependenciesno dependencies foundnot scored
  • Token-PermissionsNo tokens foundnot scored
  • Signed-Releasesno releases foundnot scored

Maintenance

19 Apr 2019
Last commit
stale
72
Commits / year
21
Contributors
recent window
None
Latest release
No GitHub releases captured

Outside contributions: 18 of 40 external pull requests merged (55% of those decided), median 0 days to merge.From the 42 most recently updated pull requests, bots excluded.

Commit activity

72 commits sampled
Mar
Jun
Sep
Dec
Jan '15
Mar
Jun
Sep
Dec
Jan '16
Mar
Jun
Sep
Dec
Jan '17
Mar
Jun
Sep
Dec
Jan '18
Mar
Jun
Sep
Dec
Jan '19
Mar

Click a bar to browse commits — or open GitHub for the full month ↓

Work rhythm

Commits by day of week

Pull request health

Resolution rate0%
Median time to merge/close: 1.2d · last 23 PRs

How fast do PRs resolve?

< 1d
11
1–3d
5
4–7d
0
1–4w
0
> 1mo
7

Days from open to merged / closed, last 23 PRs.

Pending right now7 open PRs

⚠ 7 stale PRs — open more than 60 days, no update in 30+

Long-running PRs without recent activity are usually maintainer-bandwidth signals — review process bottleneck, orphaned branches, or quietly abandoned work.

#44 Fix #43· 3363d old · waitingcheung
#56 Perf boost· 3149d old · JobLeonard

Recently merged17 PRs in the recent window

Top contributors

Issue health

Computed from GitHub Issues — no estimates. Per-issue rates use the 25 most-recently-updated issues (recent, not all-time); the open total and oldest-open age are repo-wide.

Open issues10

Total open on the repo (authoritative).

Median time to close4d

From 22 recently-closed issues. p90 6mo.

Oldest open issue9.2y

Age of the longest-open unresolved issue.

Awaiting first reply33%

1 of 3 recent open issues have no comments yet.

Stale backlog100%

3 of 3 recent open issues had no update in 30d+.

Triage gap100%

3 of 3 recent open issues are unlabeled.

What the backlog is about

AI-generated

Open issues grouped into themes by an LLM from their titles — a summary, not an authoritative classification. Numbers reflect the 3 most-recently-active open issues.

Most-wanted

Open issues with the most positive reactions — what the community is asking for.

Most-discussed

Open issues with the most comments — where the conversation is.

Labels in the recent sample

good first issue1

Per-issue rates are computed from a sample of 25 most-recently-updated issues, so they describe recent behavior rather than the all-time backlog. Reaction and comment counts come straight from GitHub.

Dependencies

Checked packages and import counts

Checked counts describe advisory coverage, not the repository’s complete dependency inventory. External imports come from a separate source-code graph.

3
Packages checked
npm
3
Direct packages checked
checked count, not total dependencies
0
Transitive packages checked
checked count, not total dependencies
Unknown
External imports
distinct modules in the captured graph

License

MIT
License
Permissive
Family
Unknown
Dep conflicts
No dependency license scan coverage
Commercial use: Generally fine for commercial and proprietary use, subject to attribution and notice terms.