Feed status · checked 2026-08-01
Huntsville Shuttle
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Alabama.
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.3, validator 8.0.1.
Checked for changes 76 minutes ago; last fetch returned HTTP 404.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 1309 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 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
360 of 360 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
912 of 912 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
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Service data ended 1309 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 360 of 360 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 912 of 912 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · 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_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's last published service date was 1309 days ago.
- 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 4 kinds of issue across 37 instances (0 error, 37 warning, 0 informational).
Service data ended 1309 day(s) ago. Trip planners have likely already dropped this feed.
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.
2 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 10).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
78 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("1st St at Castlewood Apartments", "1st St at Freeman Rd", "3257 Bob Wallace Ave", 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.
This feed has 360 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 10 (blue)
- 11 (teal)
- 1 (red)
- 2 (yellow)
- 3 (gray)
- 4 (green)
- 5 (yellow)
- 6 (pink)
- 7 (pink)
- 8 (pink)
- 9 (orange)
| Route | Type | Line color |
|---|---|---|
| 10 Pulaski Pike | Bus | blue |
| 11 UAH Campus | Bus | teal |
| 1 Brahan Spring | Bus | red |
| 2 Patton | Bus | yellow |
| 3 Holmes, UAH | Bus | gray |
| 4 University Drive | Bus | green |
| 5 Byrd Spring | Bus | yellow |
| 6 Jones Valley | Bus | pink |
| 7 Meridian, A&M | Bus | pink |
| 8 Blue Spring | Bus | pink |
| 9 Oakwood | Bus | orange |
List every stop
- 1st St at Castlewood Apartments
- 1st St at Freeman Rd
- 3257 Bob Wallace Ave
- 3599 Bob Wallace Ave
- 3801 Triana Blvd
- 4 mile Post
- 7th Day Adventist Apartments
- 9th Ave at 1st St
- 9th Ave at Seminole Dr
- Across from Royal Funeral Home
- Across from Walgreens
- Airport Rd across from Country Club Apartments
- Airport Rd at Country Club Apartments
- Andrew Jackson at Andrew Jackson Baptist Church
- Andrew Jackson at Dollar General
- Andrew Jackson at O'Shaughnessy NB
- Andrew Jackson at O'Shaughnessy SB
- Andrew Jackson at Ward NB
- Andrew Jackson at Ward SB
- Ascent Trail #1
- Ascent Trail #2
- Ascent Trail #3
- Ascent Trail at Bonnell
- Balmoral at Gleneagles NB
- Balmoral at Gleneagles SB
- Beard at Sitka
- Beard at Turf
- Benaroya at Malibu Apartments
- Blue Spring Rd at Blue Spring Cir NB
- Blue Spring Rd at Blue Spring Cir SB
- Blue Spring at Gamma NB
- Blue Spring at Gamma SB
- Blue Spring at Greenhill NB
- Blue Spring at Greenhill SB
- Blue Spring at Oakdale
- Blue Spring at Old Blue Spring Rd
- Blue Spring at Stonehurst Apartments
- Blue Spring at Stonehurst Apartments
- Blue Spring at Wilshire NB
- Blue Spring at Wilshire SB
- Blue Spring at Winchester SB
- Bob Wallace at Larry
- Bonnell at Sparkman
- Bradford & Wynn - Research Park
- Bradford at Benchmark EB
- Bradford at Benchmark WB
- Briar Green at Braeswood
- Briar Green at Hunters Ridge
- Briar Green at Vermont
- Bridge Street Town Center
- Bryant Bank and Church Street
- Byrd Spring at Dalton
- Calhoun College
- Centaur at Balwin
- Centaur at Telstar
- Central Health NB
- Central Health SB
- Charger Village
- Cheddars
- Church St at Wheeler Ave SB
- Church St at Wheeler Ave
- Church at Dallas (Old Depot)
- Church at Dallas
- Clinton Avenue Grocery
- Clinton across from Post Office
- Clinton at 4th
- Clinton at Cemetery
- Clinton at Cemetery
- Clinton at Indiana
- Clinton at Lowery
- Clinton at Parkway Access
- Clinton at Pollard
- Clinton at Seminole
- Clinton at Seminole
- Clinton at the Post Office
- Clinton at the VBC North Hall
- Cobb Rd at Villa Madrid
- Courthouse North Side
- Courthouse Westside Square
- DHR
- Dallas at Holmes EB
- Dallas at Holmes WB
- Dollar General Parking Lot
- Dr Richard Showers Recreation Center
- Drake Ave Academy Sports
- Drake Ave at All Nations Church
- Drake at Clopton
- Drake at Grote
- Drake at McVay
- East of Hanh's Alterations
- East of the Prado
- Elizabeth at Creekbend Terrace NB
- Elizabeth at Creekbend Terrace SB
- Elizabeth at Mastin Lake NB
- Elizabeth at Mastin Lake SB
- Enterprise Way and Moore Farm Ln
- Enterprise Way and Rime Village Dr NB
- Enterprise Way at Rime Village Dr SB
- Executive Dr at Downtown Rescue Mission
- Explorer Blvd at Bradford Dr NB
- Explorer Blvd at Bradford Dr SB
- Fairbanks at Alaska
- Fairbanks at Love
- Fuel City
- Gallatin St at Longwood Dr NB
- Gallatin St at Longwood Dr SB
- Gallatin St at Lowe Ave
- Gallatin at Pelham
- Holmes at Austin
- Holmes at Ben Graves EB
- Holmes at Ben Graves WB
- Holmes at Fairway
- Holmes at Galway
- Holmes at Hal
- Holmes at Jack Coleman
- Holmes at Karter WB
- Holmes at Peachtree
- Holmes at Sparkman Homes
- Hood at Knight
- Hood at Windchase
- Hsv.Madison County Public Library
- Huntsville Country Club
- Huntsville High School
- Huntsville High School
- Huntsville Hospital (Gallatin & Sivley)
- Huntsville Hospital Main
- Huntsville Museum of Art / Pane e Vino
- Huntsville Museum of Art SB
- Huntsville Rehabilitation Services
- Huntsville Summit SB
- Huntsville Summit
- Ivy and Westmill
- Ivy at Ben Garmon
- John's Store EB
- John's Store WB
- Johnson Towers
- Johnson at Triana
- Jordan Lane at Sparkman Dr NB
- Jordan Lane at Sparkman Dr SB
- Knight Rd at Phoenix House Apartments
- Knight at Twickenham Lodge Apts
- Lee's Tailoring
- Lockheed Martin Entrance
- Longwood Dr at Center for Colon & Digestive Disease
- Main Street South at Radisson Hotel
- Mastin Lake at Glendale
- Mastin Lake at Kenwood EB
- Mastin Lake at Kenwood WB
- Mastin Lake at Lakewood Baptist Church
- Mastin Lake at RSFCU
- Mastin Lake at the Post Office
- Max Luther at the Health Dept.
- Medaris at Atkins (east end)
- Medaris at Atkins (west end)
- Medaris at Burros
- Medaris at Norwood
- Meridian St at Alabama A&M
- Meridian St at Garden Cove
- Meridian St at Holloway
- Meridian at Baxter NB
- Meridian at Baxter SB
- Meridian at Chase NB
- Meridian at Chase SB
- Meridian at College Plaza NB
- Meridian at College Plaza SB
- Meridian at Delaware
- Meridian at Dollar General NB
- Meridian at Dollar General SB
- Meridian at Drake College
- Meridian at MLK School
- Meridian at Olympia Gardens Apts NB
- Meridian at Olympia Gardens Apts SB
- Meridian at Wilkenson NB
- Meridian at Wilkenson SB
- Metro Kiwanis Sports Plex
- Mexican Express
- Monroe at Church
- Monroe at the Chamber of Commerce
- Newson Rd at Cherokee Bend
- Newson at Ridgewood Apartments
- Newson at Thomas Rd
- Newson at Wedgewood Court
- North Campus Housing
- North Parkway at Regions Bank
- Oakwood across from Huntsville Country Club
- Oakwood across from Kroger
- Oakwood at Church EB
- Oakwood at Church WB
- Oakwood at Church of God EB
- Oakwood at Church of God WB
- Oakwood at Club View EB
- Oakwood at Club View WB
- Oakwood at Euclid EB
- Oakwood at Euclid WB
- Oakwood at Kroger
- Oakwood at Levert
- Oakwood at Old Winn Dixie Shopping Ctr.
- Oakwood at Orchard EB
- Oakwood at Orchard WB
- Oakwood at Suzanne Ter EB
- Oakwood at Suzanne Ter WB
- Old Madison Pike and Bocker
- Old Madison Pike at Dollar General
- Old Madison Pike at Research Park
- Old Madison Pike at Steeplechase
- Old Madison Pike/Citgo
- Parkway Place Mall
- Parkway at Texaco
- Patton at Big Oaks Apartments
- Patton at Capri Apartments
- Patton at Foster
- Patton at Holiday Foods
- Patton at Morgan NB
- Patton at Morgan SB
- Patton at Pinecrest Apartments
- Patton at Seville Apartments
- Patton at Telstar
- Poplar at Arctic
- Poplar at Beard
- Poplar at McCrary EB
- Poplar at McCrary WB
- Poplar at Yukon
- Pratt at Schiffman EB
- Pratt at Schiffman WB
- Pulaski Pike at Beasley NB
- Pulaski Pike at Beasley SB
- Pulaski Pike at Broadview NB
- Pulaski Pike at Cora Hill NB
- Pulaski Pike at Cora Hill SB
- Pulaski Pike at Country Club
- Pulaski Pike at Dunham
- Pulaski Pike at Family Dollar NB
- Pulaski Pike at Family Dollar SB
- Pulaski Pike at Kenard Ave NB
- Pulaski Pike at Kenard Ave SB
- Pulaski Pike at McEwen SB
- Pulaski Pike at Oakwood
- Pulaski Pike at Pulaski Ct NB
- Pulaski Pike at Pulaski Ct SB
- Pulaski Pike at Pulaski Pike NB
- Pulaski Pike at Pulaski Pike SB
- Pulaski Pike at Save A Lot NB
- Pulaski Pike at Save A Lot SB
- Pulaski Pike at Sparkman NB
- Pulaski Pike at Sparkman SB
- Pulaski Pike at Stag Run Dr NB
- Pulaski Pike at Stag Run Dr SB
- Pulaski Pike at Stringfield NB
- Pulaski Pike at Stringfield SB
- Pulaski Pike at Winchester Rd NB
- and 110 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 46.7 | first check |
| 2026-07-30 | 46.7 | no change |
| 2026-07-31 | 46.7 | no change |
| 2026-08-01 | 46.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1309 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning912 instances
912 of 912 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning360 instances
360 of 360 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning29 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 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.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · 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.)
Finding code: 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
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · 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.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 1309 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 1309 days ago, so FTA would find the link out of date.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 912 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. Service data expired 1309 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 1309 days ago.
- 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
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, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 80 / 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. FTA NTD readiness also checks that the published feed is valid.
- Freshness 0 / 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. FTA NTD readiness also checks that the published feed is current.
- 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/huntsville-shuttle/2026-08-01.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-08-01. 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.