DSpace User Interface built on Angular
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 23%
Response Time: 3h
First Timer Success: 17%
DSpace/dspace-angular has a recorded first-timer success rate of 16.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in DSpace/dspace-angular respond to incoming external pull requests in approximately 2.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 63.9 places DSpace/dspace-angular in the A tier.
The external contributor pull request merge rate for DSpace/dspace-angular is 23.1%, based on public PR activity from non-core contributors.
DSpace/dspace-angular currently has 26 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
DSpace User Interface built on Angular
Collaborative maintainer environment in DSpace/dspace-angular. Reviews community pull requests with focus on project quality.
Discussions in DSpace/dspace-angular focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/DSpace/dspace-angular?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (29% approval). Large PRs (>500 lines) take ~12 hours (15% approval). Keep your diff compact for rapid review.
Describe the bug On the item page, clicking an author opens /browse/author in a new tab, while other browse links, like issue date, open in the same tab Spotted on sandbox.dspace.org Confirmed this does not occur on demo.dspace.org (DSpace 10), however, this should be confirmed in the code (see next bullet) demo.dspace.org renders authors with ds-plain-text-metadata-list-element while sandbox.dspace.org uses ds-browse-link-metadata-list-element Bug is browser-independent (reproduced on Chrome v154.0 and Firefox v156) To Reproduce Compare: (not ok) https://sandbox.dspace.org/entities/publication/2574d334-41d8-481e-be5a-cf2980ee17f0 (ok) https://demo.dspace.org/entities/publication/2574d334-41d8-481e-be5a-cf2980ee17f0 Or: On sandbox.dspace.org, go to /browse/author, select any author and open any publication that does not have relationships to Person entities (so authors are displayed as a list) Observe: click an author and it opens in a new tab. Click the date and it stays in the s
Describe the bug Anonymous users can tell whether an item has a draft version in progress (due to presence of Version History table, see screenshot above), even though the REST contract explicitly says they should not be able to: Due to the restriction applied to this flag anonymous users will be unable to discover that a new version is currently under review. Source: https://github.com/DSpace/RestContract/blob/main/versionhistories.md#linked-entities Observed on sandbox.dspace.org. To Reproduce Ensure the REST API has versioning enabled (true on sandbox.dspace.org). Go to any Item that does not have any version. Observe that no Version History table is shown. Log in as admin, create a new version of the Item (do not deposit it). Open Item page in a new window (incognito mode). Note the Version History table is shown with a single record. Expected behavior Anonymous users should not be able to discover that a new version is under review. The Version History table should be shown o
Description Angular 22 is now available (as of June 2026), so we should upgrade our User Interface (currently running Angular 20) to the latest version. If an upgrade to Angular 22 is complicated, then we should minimally upgrade to Angular 21 (released in Nov 2025) As part of the upgrade, we should also investigate whether it's easy to backport any Angular upgrade to DSpace 10.x and/or 9.x. For the Angular 20 upgrade in DSpace 10.0, we found the upgrade could be backported to 9.x. This may not always be possible, but it's worth keeping in mind. Resources: Angular update guide: https://angular.dev/update-guide https://blog.angular.dev/announcing-angular-v22-c52bb83a4664 https://blog.angular.dev/announcing-angular-v21-57946c34f14b Our prior upgrade to 20.0: #4804 Tentatively scheduling for 11.0, but this needs a volunteer to investigate the complexity of this upgrade. Related work Updating our Node/NPM requirements (as noted in #6245) may require an upgrade to Angular 22 as it's t
Describe the bug Current documentation requires Node v20, v22 or v24. By the time DSpace 11 ships, v22 and v24 will be EOL and v26 will be Current LTS. We should consider raising the requirement to at least v24, preferably v24 or v26. This also affects NPM: the current requirement ties it down at v10. We should investigate the work which may be required by these proposed upgrades. Related work #6165 discusses a warning that arises when building for Node v24.
Is your feature request related to a problem? Please describe. Upgrade to Angular v18 was finalized in DSpace 9.0 (#3304). However, Jasmine/Karma is still used for unit tests but, as noted in the issue, Karma is deprecated. Angular v21 declared stable support for Vitest. This is also the Angular team's default choice for new projects in v21+ (moreover, Angular team also provided a guide on Migrating from Karma to Vitest, so the migration can be semi-automated.) I'd like us to discuss and plan a migration away from Karma to a modern test runner. From what I can see, the most commonly mentioned options are: Vitest (default in Angular >=v21) Jest (has been around longer) Web Test Runner (runs tests in a real browser rather than Node/jsdom) Vitest and Jest are both a test runner and a testing library, so they replace both Karma + Jasmine stack. Web Test Runner replaces only Karma (uses bult-in Mocha framework support, but has Jasmine adapter web-test-runner-jasmine). Also, check out Vite
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to DSpace/dspace-angular, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of DSpace/dspace-angular acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 23.1% were successfully merged into the primary branch.
DSpace/dspace-angular has a recorded first-timer success rate of 16.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 63.9 places DSpace/dspace-angular in the Welcoming tier.
The external pull request merge rate is 23.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, DSpace/dspace-angular currently has 26 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for DSpace/dspace-angular are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.