ARI² — the Author Research Integrity Risk Index, validated and published, screens an author's bibliometric profile for commercial-authorship and paper-mill patterns. JPI² (Beta — calibration in progress) — the Journal Publishing Integrity Risk Index, screens a journal's public metrics for the same family of patterns at the venue level. Free, open-source, built entirely on public data. Each reading tells you where to look — not what to conclude.
New JPI² is now archived on Zenodo — DOI: 10.5281/zenodo.20712630 Read it → ARI² The ARI² preprint — read on Zenodo or SSRN Read it →ARI² is the first author-level bibliometric tool specifically designed to detect commercial-authorship and paper-mill patterns using only public data. It combines four signals into a composite score. In the pilot feasibility study (28 source-verified authors), ARI² achieved an AUC of 0.938 (p = 0.003) for distinguishing paper-mill cases from controls. A high score is a scientifically validated prompt to stop, review, and verify — then apply fair human judgment.
Choose automatic lookup (recommended) to let the tool fetch all data directly from OpenAlex, or enter values manually if you already have them.
Type the author's name to find their OpenAlex profile, then click the matching author. The tool automatically retrieves every value needed for ARI² — including co-authors and retractions — directly from OpenAlex and shows the result.
Search for an author and click their name to see the ARI² result.
Enter all values and click Calculate to see the ARI² score.
The automatic lookup handles all data retrieval for you. The guide below explains how to find the OpenAlex Author ID and how to obtain co-author and retraction data manually if you prefer the manual entry mode.
In the Automatic Lookup tab of the calculator above, type the author's full name and click Search. The tool searches OpenAlex and returns matching author profiles.
Click on the correct author from the results. Verify first by checking the institution, field, and country, since multiple authors with the same name may appear. As soon as you click, the tool retrieves the author's full works list from OpenAlex, counts unique co-authors across all publications, counts retracted works, and calculates all four signals and the composite ARI² score. A progress bar shows the status for authors with large publication records.
What is computed automatically: Works count, Citations, h-index — from the author profile. Unique co-authors — by collecting all co-author IDs across all works and counting each person once. Retractions — by counting works where OpenAlex has flagged is_retracted = true.
No separate button, no downloads, no exports, no manual counting needed.
If the correct author does not appear in the results, try a different spelling, add the institution name, or use the Manual Entry mode with values obtained directly from openalex.org.
Search for the author by name on openalex.org. Select Authors in the category filter. Click the correct profile and verify using institution and field.
The unique co-author count is not displayed directly on the author profile page. It requires fetching the author's works data. The simplest method: copy the author ID from the page URL (the part starting with A followed by digits), then use the following API call in your browser address bar.
Easier alternative: Use the Automatic Lookup mode. It performs this entire process for you and shows the co-author count before calculating the score.
Automatic Lookup is strongly recommended for all users.
The Automatic Lookup mode detects retractions from OpenAlex's is_retracted field, which is the same source used in the original ARI² research. OpenAlex's retraction detection is not exhaustive — some retractions are indexed later than others. Retraction Watch is the most comprehensive retraction database and should be used to cross-check the result for high-stakes editorial assessments.
When to cross-check with Retraction Watch: When the automatic lookup returns a non-zero retraction count and you need to verify the exact number. When the automatic lookup returns zero but you have reason to suspect retractions exist. Before taking any formal editorial action based on a High score band result.
For routine screening, OpenAlex retraction data is sufficient. For formal proceedings, always verify against Retraction Watch.
Visit retractionwatch.com/retraction-watch-database and search by the author's full name. Count the total retracted papers listed. If a discrepancy exists between OpenAlex and Retraction Watch, use the higher count and enter it manually using the Manual Entry mode.
This is a stable reference for understanding ARI² before running a search. The live Signal Profile panel shown with every result explains your specific reading; the cards below explain what each signal means in general. Every signal is a public-record screening cue — never a misconduct finding. Tap a card to expand it.
Consistent with the ARI² manuscript, which formally defines Signals A–D and emphasizes that moderate or high outputs warrant contextual human review rather than automatic judgment. For what the overall score bands mean, see ARI² Interpret below.
ARI² scores are calibrated against the 28-author pilot cohort. Score bands are exploratory heuristics — not validated cut-offs. Every flag requires human review and contextual assessment before any decision is taken.
Calibration caveat: Scores are normalized against the 28-author pilot cohort (Kelleni 2026) and are not yet externally validated. Authors whose profiles fall outside the pilot range may receive scores below 0 or above 100 — these should be read qualitatively. For the full open-source scoring pipeline, see the Zenodo repository. A validated reference population is under development.
The Journal Publishing Integrity Risk Index (JPI²) is the venue-level companion to ARI². JPI² is in Beta: its observational-signal thresholds are provisional and reference-class calibration is still in progress, so every reading should be treated as exploratory rather than final. Enter a journal name to see whether its public metrics show signs that warrant careful review. As with ARI², a high reading is not a verdict — and the tool never labels a named journal "predatory" or "a paper mill." It reports a risk signal and the evidence behind it, which is a fair basis to investigate further, and nothing more. Editors and publishers can also use it to screen their own journals proactively for early signs of special-issue infiltration, before retractions accumulate. v1.3.1 runs J-A (retraction burden, band-driving) live from OpenAlex with Crossref/Retraction Watch confirmation, plus J-B, J-C, J-D, and J-G (the ARI²-bridge signal) as observational. See the interpretation guide below.
Type a journal title to find it on OpenAlex. Confirm the exact journal — publisher and ISSN are shown — before reading the result; matching the wrong journal to a score is something this tool is built to avoid.
Search for a journal or pick an example to see its screening profile.
A JPI² reading describes public-record signals, not a verdict. The headline is not a single 0–100 score. In v1.3.1 it is chosen by rule-based severity tiers: the lead retraction-burden signal (J-A) can drive a Moderate or Elevated headline on its own, and observational signals (output-burst, issue concentration, topic concentration, author-network patterns) can escalate a reading even when J-A is low. See the JPI² Interpret section below for what each headline state means.
JPI² is a multi-signal index, not a retraction-only tool. Each signal answers one specific question about the journal's public record. The live tool's Signal Profile panel (shown with every result) reports the current status of every signal below for the journal you search — this glossary explains what each one means and how reliable it currently is.
This is why the JEPH and NEJM cases in the manuscript matter for reading any single result: JEPH was missed because J-A sat below the Moderate cut and the observational signals did not escalate; NEJM over-escalated because J-D alone read high before reference-class calibration existed. A signal's current reliability is part of how it should be weighed, not just its value.
Why the headline is not always J-A. Letting the retraction-burden signal alone drive the headline would mean that a journal with missing or zero-coverage retraction data (which the tool cannot always distinguish from genuinely clean) would receive a green band by default. That is a false reassurance, which is as harmful as a false alarm — and worse, it would be the harm that hurts the user trying to choose where to submit. JPI² is architected so that observational signals (J-B output-burst, J-C issue concentration, J-D topic concentration) can override a J-A-only headline whenever they show strong anomalies.
Why some signals are observational, not band-driving. J-A has a calibrated reference range (the 0.21% baseline from peer-reviewed retraction-rate studies, plus the 10× factor seen in captured journals). J-B, J-C, and J-D do not yet have calibrated cut-points across the full reference-class normalisation (size, open-access model, discipline, age). Until calibration is complete, they are shown as observations — informative for the reader, but never used alone to issue a coloured band. This is intellectually honest and protects against false flags on legitimate large-scale venues.
A reading is a question, not an answer. Every JPI² output is the start of a careful review, never the end of one. The evidence panel directly links to the public sources used to compute the signals — verify everything for yourself. Common legitimate explanations include a clean-up phase after external misconduct, or a specialised topic with naturally narrow citation distribution. See the due-process checklist below for the full verification steps before drawing any conclusion.
v1.3.1 coverage and limitations. JPI² currently runs J-A (band-driving, via OpenAlex is_retracted with Crossref/Retraction Watch confirmation) plus J-B, J-C, J-D, and J-G (the ARI²-bridge: simplified ARI² signals aggregated across the journal's recent first-authors) as observational signals. J-F (content anomaly via Problematic Paper Screener) is specified in the methods document and not yet wired. Provisional weights and reference-class normalisation thresholds are non-portable and exploratory until calibrated on a large journal sample. The methods specification (in preparation) will document the validation procedure and the discriminant statistics in detail.
Every JPI² reading resolves to one of the five states below. The headline is not a single 0–100 score. In v1.3.1 it is chosen by rule-based severity tiers: the lead retraction-burden signal (J-A) can drive a Moderate or Elevated headline on its own, and observational signals can escalate a reading even when J-A is low — never the reverse. Each reading is accompanied in the tool by a Signal Profile panel showing the primary driver and the status of every signal. As with ARI², a reading is a screening signal and a basis for review — never a verdict.
Why this is a profile, not a score. JPI² v1.3.1 issues a headline from severity-tiered rules across its signals, not from a single weighted number. The per-signal weights shown in the methods paper are provisional parameters for a future composite and are not applied in the current headline. Presenting a single 0–100 score now would imply a precision the provisional thresholds cannot yet support \u2014 so the tool reports a structured Signal Profile instead. For the full reasoning behind each signal and the architecture, see the JPI² Guide above.
The Publication-Pattern Geographic Diversity Index (PPGDI) is an exploratory companion metric to ARI². It captures the breadth of geographic spread across an author's co-author network and may help identify unusual international collaboration patterns associated with commercial authorship behaviour.
What PPGDI measures: PPGDI is computed as the ratio of unique co-author countries to total unique co-authors. A value approaching 1 means nearly every co-author comes from a different country — an unusual pattern in normal academic collaboration. A low value indicates concentrated, locally coherent networks.
When it is most relevant: PPGDI carries the most interpretive weight when combined with a high Signal A (Network Fragmentation) score. In the pilot dataset, PPGDI showed potentially meaningful group-level differences and may help capture cross-geographic collaboration anomalies associated with commercial authorship. Alone, however, it cannot distinguish legitimate international collaboration from suspicious dispersal.
Future versions will compute PPGDI automatically from OpenAlex institution-level country metadata. Currently, manual entry is required. The co-author count used here should match the value entered in the ARI² calculator.
Enter the number of unique countries represented across your author's co-author network. The co-author count carries over automatically from your ARI² calculation above.
Enter co-author countries and total co-authors to calculate PPGDI.
| PPGDI Pattern | Interpretation | Action |
|---|---|---|
| Low PPGDI (< 0.15) | Limited geographic dispersion; locally or regionally concentrated collaboration | No additional concern from geographic signal |
| Moderate PPGDI (0.15 – 0.35) | Mixed or regionally diverse collaboration; common in established international networks | Standard contextual review |
| High PPGDI (> 0.35) | Broad geographic dispersion requiring contextual interpretation | Review in context of full ARI² profile |
| High PPGDI + High Signal A | Potentially more relevant to commercial-authorship pattern; network may be transactional rather than collaborative | Include in due-process checklist review |
| High PPGDI alone | Not diagnostic; may reflect entirely legitimate international collaboration in global research networks | No action on PPGDI alone |
The current ARI² is primarily a retrospective risk index: Signal B (Retraction Burden) means the index reaches full discriminative power only after retractions have occurred. A prospective extension — ARI²-PM — is under development, aiming to detect anomaly signals earlier in the publication cycle.
ARI² is currently best understood as a retrospective author-level research-integrity risk index with prospective potential. A future ARI²-PM module may integrate retraction-free collaboration anomalies for earlier detection of commercial authorship patterns — potentially before any retractions have been registered.
Candidate signals under investigation for ARI²-PM include the following. Each requires further empirical validation before inclusion in a scored index.
Researchers interested in collaborating on ARI²-PM validation are welcome to contact the developer at drthabetpharm@yahoo.com. All methodological development will be documented openly via the Zenodo repository.
A moderate or high ARI² score, or a Moderate/Elevated JPI² reading, is a prompt to stop, review, and verify — then judge fairly. The checklists below must be applied before any editorial, institutional, or publishing decision is taken. A reading tells you where to look. It does not tell you what to conclude. That is a feature, not a limitation.
Confirm via ORCID. Name disambiguation errors in OpenAlex can inflate co-author counts for authors with common names. Ensure the profile has not merged multiple distinct researchers.
Compare author records across Google Scholar, Scopus, OpenAlex, and institutional profiles. Discrepancies in publication counts, h-index, or affiliation may indicate profile-merging artefacts rather than genuine anomalies.
Is high co-author count normal in this field? Large consortium science and clinical trial networks legitimately produce high Signal A values.
Is the author early-career? High output may reflect a productive lab. Is the elevated signal recent or consistent across the full career?
Are retractions from a single event or distributed across multiple journals and years? The pattern matters as much as the count.
Do co-authors appear across many unrelated papers? Are many one-time collaborators from geographically and institutionally unconnected locations?
Were many papers submitted to the same journal cluster or known predatory publishers? Unusual special-issue clustering warrants scrutiny.
ARI² flags trigger investigation — never automatic rejection. All decisions must follow institutional due-process procedures and allow the author to respond — see the right-of-reply channel below. No author should face any consequence based solely on a score.
Confirm retraction counts and dates in Retraction Watch and Crossref. OpenAlex's is_retracted flag is the fastest live source but can lag behind very recent retraction notices.
Has the journal, its editorial board, or its publisher already issued a public statement, expression of concern, or retraction notice explaining the cause? A high reading during transparent cleanup is a sign of accountability, not concealment.
Many documented paper-mill captures concentrate in one or two guest-edited special issues. Check whether the J-C issue-concentration signal and the retraction dates point to a contained episode rather than a journal-wide pattern.
Has the editorial board changed since the flagged period? Has the publisher (e.g. via COPE membership or public notices) responded with a documented remediation process?
Megajournals can carry high absolute retraction counts while remaining clean on a normalised (J-A) basis; narrow specialist journals can show naturally high topic concentration (J-D) without misconduct. Check the journal's current DOAJ, Scopus, or Web of Science status for independent corroboration.
J-B, J-C, J-D, and J-G are provisional and not yet reference-class calibrated (see the JPI² Guide). They support or qualify the J-A reading; none of them alone should be treated as confirming a pattern.
Use the right-of-reply channel below before drawing or publicising any conclusion. Verified context from the journal will be noted in the instrument's documentation.
JPI² flags warrant investigation — never automatic delisting, citation refusal, funding consequence, or reputational sanction against the journal, its editors, its publisher, or any author who has published there.
ARI² scores are probabilistic risk indicators, not determinations of misconduct. A high score reflects a statistically unusual publication pattern that warrants human review and contextual investigation — not automatic sanction. No author should face rejection, retraction, defunding, or any professional consequence based solely on an ARI² score. The index is a screening aid. Misuse of this index to make adverse decisions without adherence to due process would be both ethically unsound and legally perilous.
Likewise, JPI² readings are public-record screening signals about a journal's published output, not determinations of misconduct by the journal, its editors, its publisher, or any author who has published there. An elevated reading reflects a statistically unusual pattern that warrants independent investigation under established procedures (e.g. COPE) — not automatic delisting, citation refusal, funding consequence, or reputational sanction. The index is a screening aid. Misuse of this index to make adverse decisions against a journal or its contributors without adherence to due process and an opportunity to respond would be both ethically unsound and legally perilous.
This tool uses only publicly available bibliometric data from OpenAlex and the Retraction Watch Database. No human subjects are recruited, contacted, or experimented upon. Named case authors in the validation study were identified exclusively through documented public records.
The due-process framework embedded in this tool reflects the author's commitment to responsible and proportionate use of bibliometric risk indicators. ARI² and JPI² are screening aids — never a verdict. Any use of either index that bypasses the relevant due-process checklist, stigmatises researchers or journals without contextual review, or substitutes a reading for expert judgement would be contrary to the intent and spirit of this work.
For licensing, attribution, and permitted reuse, see the Rights, Licensing & Attribution section below.
This section describes what you may do with the Kelleni Index / ARI² website, code, and methodology — and how to attribute and cite it correctly.
| Content type | Licence | What this means for you |
|---|---|---|
| Website text, explanatory materials, and figures Sections, descriptions, interpretation guidance, guides |
CC BY 4.0 | Share and adapt freely with attribution. Indicate if changes were made. Do not imply endorsement. |
| Analytical code and scoring pipeline JavaScript calculator, Python analysis code, normalization parameters |
Apache 2.0 | Use, modify, and distribute freely including commercially. Retain the copyright notice and licence file. State changes made to the original. |
| Research dataset 28-author pilot cohort, signal values, PPGDI data (Zenodo) |
Apache 2.0 | Freely reusable for research and validation. Cite the Zenodo repository. Do not present the pilot dataset as an exhaustive or externally validated reference population. |
“Kelleni Index” is used as the project name identifying the original ARI² index, its scoring methodology, and this implementation. It is not a registered trademark, but it identifies an original research contribution and is used here to distinguish this work from adapted or derived implementations.
Adapted or modified implementations of ARI² are permitted under the Apache 2.0 licence and encouraged for further research. However, they must clearly indicate any changes made to the original scoring rules, weights, or normalization parameters, and must not imply endorsement by the original author, official affiliation with this project, or methodological equivalence with the Kelleni Index unless the original scoring rules are preserved in full.
In practice: if you change the signal weights, add signals, or re-normalize against a different reference cohort, your implementation is a derivative — please name it accordingly and link back to the original.
Currently PPGDI requires manual entry of unique co-author country counts. The next planned upgrade will compute this automatically from OpenAlex institution metadata — the same API already used for Signal A.
institutions.country_code from each work’s authorship records during the existing OpenAlex fetch. Fully reproducible, no manual counting, consistent with the manuscript methodology.work.authorships[].institutions[].country_code for all co-authors, then computes unique country codes ÷ unique co-author IDs. No additional API calls required — runs within the same OpenAlex request already used for Signal A.
A transparent record of each instrument's publication journey — from preprint through peer review to final publication. Completed milestones are shown below with their DOIs; pending stages update as the work progresses.