Feed status · checked 2026-07-18
Waltti (Lappeenranta)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Etelä-Karjala, Finland.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.2, validator 8.0.1.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid url (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
1089 of 1089 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
3407 of 3407 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed states that service is published through 2080-12-31. This may be intentional or a placeholder; confirm current service with the transit operator.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 11 kinds of issue across 28055 instances (1083 error, 26936 warning, 36 informational).
Service is published through 2080-12-31. It may be intentional, but confirm the end date before treating the feed as maintained.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
8 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Oksasenkatu / Kauppatori", "Ahvenlammentie/Kuutostie P", "Keskuskatu/Annukantie Joutsenoon", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (green)
- 100 (green)
- 1001 (green)
- 1003 (green)
- 101 (green)
- 1011 (green)
- 1012 (green)
- 110 (green)
- 111 (green)
- 112 (green)
- 113 (green)
- 114 (green)
- 12 (green)
- 120 (green)
- 121 (green)
- 130 (green)
- 130 (green)
- 14 (green)
- 1X (green)
- 2 (green)
- 200 (green)
- 201 (green)
- 21 (green)
- 22 (green)
- 23 (green)
- 24 (green)
- 25 (green)
- 2H (green)
- 3 (green)
- 300 (green)
- 301 (green)
- 3K (green)
- 4 (green)
- 5 (green)
- 500 (green)
- 601 (green)
- 602 (green)
- 603 (green)
- 604 (green)
- 610 (green)
- 620 (green)
- 7 (green)
- 8 (green)
| Route | Type | Line color |
|---|---|---|
| 1 Yliopisto-Keskusta-Kiiskinmäki | Bus | green |
| 100 Lappeenranta-Joutseno-Imatra | Bus | green |
| 1001 P1 Kiiskinmäki | Bus | green |
| 1003 P3 Kivisalmi | Bus | green |
| 101 LUT-yliopisto-Joutseno-Imatra | Bus | green |
| 1011 SaiPa Yliopisto-Keskusta-Jäähalli | Bus | green |
| 1012 SaiPa Kivisalmi-Keskusta-Jäähalli | Bus | green |
| 110 Joutseno-Lpr | Bus | green |
| 111 Lpr-Joutseno-Imatra | Bus | green |
| 112 Imatra-Joutseno-Lpr | Bus | green |
| 113 Lpr-Joutseno | Bus | green |
| 114 Lpr-Joutseno, loma | Bus | green |
| 12 Kivisalmi-Yliopisto-Keskusta-Karhuvuori-Lauritsala | Bus | green |
| 120 Joutseno-Ravattila-Konnunsuo-Kivisaari | Bus | green |
| 121 Joutseno-Ahola-Kuurmanpohja-Ravattila | Bus | green |
| 130 Lpr-Partala-Soskua | Bus | green |
| 130 Ravonsydän - Keskusta | Bus | green |
| 14 Mäntylä-Keskusta-Karhuvuori-Mustola | Bus | green |
| 1X Yliopisto-Keskusta | Bus | green |
| 2 Kivisalmi-Keskusta-Hovinpelto | Bus | green |
| 200 Lpr-Nuijamaa | Bus | green |
| 201 Lpr - Nuijamaa, loma | Bus | green |
| 21 Vuoksenniska-Imatrankoski-Keskusasema-Vuoksenniska | Bus | green |
| 22 Vuoksenniska-Keskusasema-Imatrankoski-Vuoksenniska | Bus | green |
| 23 Huhtanen-Vuoksenniska-Keskusasema-Imatrankoski-Jakola | Bus | green |
| 24 Tainionkoski-Imatrankoski-Salo-Issakka | Bus | green |
| 25 Imatrankoski-Keskusasema-Kylpylä | Bus | green |
| 2H Hovinpelto-Matkakeskus-Keskusta | Bus | green |
| 3 Puhakankatu-Keskusta-Kivisalmi | Bus | green |
| 300 Lpr-Vainikkala | Bus | green |
| 301 Lpr-Vainikkala, loma | Bus | green |
| 3K Kivisalmi-Kesämäki | Bus | green |
| 4 Karhuvuori-Keskusta-Mäntylä | Bus | green |
| 5 Yliopisto-Keskusta-Matkakeskus | Bus | green |
| 500 Turkkila-Rutola-Sammonlahti | Bus | green |
| 601 Hujakkala-Ylämaa-Lpr | Bus | green |
| 602 Lpr-Pulsa-Ylämaa | Bus | green |
| 603 Lpr-Hytti-Ylämaa | Bus | green |
| 604 Lpr-Ylämaa-Hujakkala | Bus | green |
| 610 Lpr-Simola-Rikkilä | Bus | green |
| 620 Lpr-Pulsa-Tani | Bus | green |
| 7 Mustola-Keskusta | Bus | green |
| 8 Rutola-Ruoholampi-Keskusta-Pikisaari-Kariniemi | Bus | green |
This feed has 1089 stops.
List every stop
- Koskenkoulu
- Saarenkatu
- Kariniementie
- Happotie
- Oksasenkatu / Kauppatori
- Huhtasen koulu
- Helsingintie P
- Helsingintie E
- Karjalantie 89
- Karjalantie 89
- Ylämaantie 341
- Ylämaantie 347
- Ylämaantie 805
- Ylämaantie 807
- Ylämaantie 2169
- Ylämaantie 2396
- Ylämaantie 2492
- Ylämaantie 2498
- Pentintie th P
- Pentintie th E
- Ylämaantie 2968
- Ylämaantie 3005
- Ylämaantie 3016
- Koskenkylä P
- Koskenkylä E
- Rikkiläntie 1281
- Rikkiläntie 1276
- Rikkiläntie 1219
- Rikkiläntie 1218
- Rikkiläntie 31
- Rikkiläntie 51
- Rikkiläntie 108
- Rikkiläntie 159
- Ruohiantie 278
- Joutsenontie 50
- Joutsenontie 55
- Joutsenontie 360
- Joutsenontie 368
- Joutsenontie 568
- Joutsenontie 577
- Joutsenontie 728
- Joutsenontie 732
- Joutsenontie 834
- Saimaantie 14
- Saimaantie 14
- Penttiläntie 13, Joutsenon koulukeskus
- Penttiläntie 26 P
- Penttiläntie 26 E
- Penttiläntie 141
- Penttiläntie 158
- Penttiläntie 369
- Penttiläntie 369
- Penttiläntie 433
- Penttiläntie 438
- Penttiläntie 520
- Penttiläntie 529
- Penttiläntie 653
- Penttiläntie 656
- Saimaantie 36
- Saimaantie 62
- Saimaantie 64
- Putkinotkontie 25 E
- Putkinotkontie 25 P
- Viipurintie 330
- Viipurintie 662
- Vallinkoski 171
- Asematie 2
- Asematie 9
- Asematie 9
- Rauhantie 58
- Rauhantie 68
- Rauhantie 41
- Rauhantie 84
- Tiuruniementie 36
- Tiuruniementie 46
- Tiuruniementie 87
- Tiuruniementie 94
- Niskapietiläntie 105 P
- Niskapietiläntie 104 E
- Kuusela P
- Kuusela E
- Niskapietiläntie 110 P
- Merenlahdentie 228
- Tilsalankatu th I
- Tilsalankatu th L
- Pajarilantie 118
- Pajarilantie 178
- Pajarilantie 181
- Pajarilantie 306
- Pajarilantie 309
- Pajarilantie 395
- Pajarilantie 453
- Pajarilantie 457
- Pajarilantie 520
- Utrasaarentie 50
- Utrasaarentie 92
- Utrasaarentie 98
- Utrasaarentie 130
- Utrasaarentie 135
- Utrasaarentie 174
- Utrasaarentie 174
- Muukonniemi
- Kaarnantie 20
- Kaarnantie 28
- Kaarnantie 85
- Kaarnantie 88
- Kaarnantie 113
- Kaarnantie 121
- Kaarnantie 143
- Kaarnantie 144
- Kaarnantie 191
- Kaarnantie 197
- Kaarnantie 223
- Kaarnantie 231
- Kaarnantie 277
- Kaarnantie 283
- Kaarnantie 300
- Kaarnantie 442
- Kaarnantie 446
- Ilottulantie 225
- Ilottulantie 228
- Ilottulantie 276
- Ilottulantie 282
- Ilottulantie 340
- Ilottulantie 339
- Ilottulantie 428
- Ilottulantie 459
- Ilottulantie 430
- Ilottulantie 461
- Haukilahdentie 619
- Haukilahdentie 614
- Haukilahdentie 538
- Haukilahdentie 533
- Haukilahdentie 501
- Haukilahdentie 494
- Haukilahdentie 479
- Haukilahdentie 475
- Haukilahdentie 422
- Haukilahdentie 419
- Haukilahdentie 378 L
- Haukilahdentie 378 I
- Haukilahdentie 108
- Haukilahdentie 47
- Haukilahdentie 82
- Haukilahdentie 39
- Haukilahdentie 46
- Haukilahdentie 46
- Haukilahdentie 40
- Haukilahdentie 37
- Teollisuustie th L
- Teollisuustie th I
- Honkalahdentie th E
- Haukilahdentie 18
- Konnuntie 589
- Pulp P
- Silmukuja th E
- Silmukuja th P
- Uus-Ahvenlammentie th E
- Vanha-ahvenlammentie th P
- Ahvenlammentie 28
- Ahvenlammentie 26
- Ahvenlammentie/Kuutostie P
- Karjalaisentie 9
- Messutie th P
- Messutie th E
- Lappeentie 2 I
- Lappeentie 2 L
- Lappeentie 46 I
- Lappeentie 46 L
- Lappeentie 9
- Taimitarhantie th I
- Taimitarhantie th L
- Kastarintie th I
- Kastarintie th E
- Lappeentie 302
- Lappeentie 309
- Rantatie 122
- Rantatie 136
- Rantatie 231
- Rantatie 238
- Rantatie 330
- Rantatie 335
- Rantatie 453
- Rantatie 457
- Rantatie 530
- Rantatie 541
- Rantatie 590
- Rantatie 598
- Rantatie 643
- Rantatie 651
- Rantatie 710
- Rantatie 715
- Rantatie 768
- Rantatie 774
- Aholantie 609
- Aholantie 626
- Aholantie 664
- Aholantie 671
- Aholantie 730
- Aholantie 738
- Aholantie 800
- Aholantie 812
- Aholantie 840
- Navetanmutka
- Navetanmutka
- Vuoksenniskantie 90
- Paperharjuntie 57
- Paperharjuntie 57
- Paperharjuntie 43
- Paperharjuntie 1
- Paperharjuntie 1
- Tainionkosken koulu
- Tainionkosken koulu
- Ritikanranta P
- Ritikanranta E
- Keskuskatu-Ritvankuja
- Keskuskatu-Ritvankuja
- Korvenkannantie 18
- Korvenkannantie 18
- Saareksiinmäki I
- Saareksiinmäki L
- Veteraanitalo
- Veteraanitalo
- Ensontie 55
- Ensontie 55
- Kaukopäänkatu
- Kaukopäänkatu
- Teppanala
- Teppanala
- Imatrankoskentie 20
- Huminan mutka
- Kaukopäänkatu 6
- Vuoksenniskantie 97
- Vuoksenniska P
- Vuoksenniska E
- Torikatu 1
- Torikatu 1
- Vuoksenniskantie 48 P
- Vuoksenniskantie 48 E
- Lakasenpelto
- Lakasenpelto
- Mäntyrinne
- Mäntyrinne
- Vuoksenniskantie 31
- Vuoksenniskantie 31
- Keskuskatu-Karhumäenkatu
- Joutsenonkatu 45
- Joutsenonkatu 45
- Paperharjuntie 4 P
- Paperharjuntie 4 E
- and 839 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
15 findings, ordered by severity.
Show every finding
- Error1083 instances
Invalid url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: invalid_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning26926 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3407 instances
3407 of 3407 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1089 instances
1089 of 1089 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning5 instances
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Validator rule: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info15 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info10 instances
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. The feed also carries 1083 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.
- Correctness 45 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
- Rider experience 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/waltti-lappeenranta/2026-07-18.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-07-18. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.