GTFS Scorecard
← All agencies

Feed status · checked 2026-08-27

BAS.MY Kangar

Based on the official feed source on file

Service mode Bus

66.8 / 100

up 3.9 since 2026-08-26 · D → D

Catalogued in Perlis, Malaysia.

Covers 126 daysAccessibility gaps

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 3 hours ago; last changed 3 hours ago.

Measured 4 of 4 score categories from the official feed URL on file.

How we measured this

Confidence in this measurement: high.

  • All four score categories were measured this run.
  • Realtime was sampled in one bounded window of 3 snapshots.
  • The feed was downloaded from the official feed URL on file.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

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

267 of 267 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

Fix 02

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

140 of 140 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

Fix 03

Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool

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.

⏱ Two fields, set once in export settings.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
267 of 267 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
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.

  1. 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. See this feed's finding-clearance log.

  2. 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. See this feed's finding-clearance log.

  3. Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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. See this feed's finding-clearance log.

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 is in 126 days.
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
One or more realtime feeds were reachable; live-arrival coverage is not known.

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

Correctness69.5 / 100

The MobilityData validator flagged 6 kinds of issue across 375 instances (0 error, 373 warning, 2 informational).

Freshness85.0 / 100

Service data covers the next 126 days.

Rider experience24.5 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 15 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("TMN SENA INDAH/ TMN NORMA", "UNIMAP JEJAWI/SK JEJAWI", "ALOR LANCANG/TMN SAUJANA IDAMAN", 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.

Realtime quality96.7 / 100

Sampled 3 times: 1 of 1 configured feed healthy; 85.7% of vehicles on their route.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 267 stops.

Skip to route and stop data

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.

  • R14 (red)
  • R13 (red)
  • R12 (red)
  • R11 (red)
Routes in BAS.MY Kangar's feed
RouteTypeLine color
R14 KANGAR - ALOR SETAR VIA JITRABusred
R13 KANGAR - ALOR SETAR VIA KUALA SANGLANGBusred
R12 KANGAR - KUALA PERLISBusred
R11 KANGAR - PADANG BESARBusred
List every stop
  • TERMINAL BAS SHAHAB PERDANA
  • Hospital Alor Setar
  • TERMINAL BUKIT LAGI KANGAR
  • TERMINAL PADANG BESAR PERLIS
  • HENTIAN KAMPUNG SEBERANG RAMAI
  • KAYANGAN SQUARE KANGAR
  • KOMPLEKS ISLAM PERLIS
  • PEJABAT POS LAJU
  • TMN SENA INDAH/ TMN NORMA
  • TABUNG HAJI SERIAB
  • SK SERI PERLIS
  • GIANT KANGAR cp
  • SK RAJA SYED ALWI
  • BALAI BARU
  • SK PAYA cp
  • SMK DATO SHEIKH AHMAD cp
  • SMA ALMAAD
  • MAKAM DIRAJA cp
  • BATAS LIKU ARAU
  • TMN SENA
  • TMN PROGRESIF
  • UNIMAP JEJAWI/SK JEJAWI
  • MAJLIS PERBANDARAN KANGAR (JEJAWI)
  • MASJID MUHAMMADI CP
  • SMK SYED SIRAJUDDIN CP
  • ALOR LANCANG/TMN SAUJANA IDAMAN
  • UNIVERSITI MALAYSIA PERLIS JEJAWI KANGAR
  • KG ALOR ARA
  • KG SALANG cp
  • BATU 2
  • BATU 3 1/4
  • BATU 3 1/2
  • MASJID SIRAJUDDIN
  • KG PENGHULU CHOH
  • RTM PADANG PAUH
  • PADANG PAUH
  • ALOR SENA
  • PAYA
  • KOMPLEKS PERTANIAN
  • KG BESERI / KG BUKIT TENIANG
  • SK BESERI cp
  • TMN BESERI PAYA
  • SG BATU HAMPAR
  • MRSM BESERI CP
  • IKM BESERI
  • PERKUBURAN CINA BERSERI
  • TOK MEK
  • SEMADONG
  • KG PAYA KELADI
  • PUSAT SERENTI
  • MASJID AL-MUSTAGFIRIN
  • SG JAROM
  • KG TITI TINGGI HILIR CP
  • MASJID AL-AZIM cp
  • TITI TINGGI
  • UNICITI PERLIS
  • KG BARU
  • MASJID AL-NUR CP
  • KG SERI AMAN PERLIS
  • FELCRA LUBUK SIREH CP
  • SMK RAJA PUAN MUDA TENKU FAUZIAH
  • BATU 16
  • MASJID JABAL AL-ALA CP
  • BATU 16 1
  • SMK RAJA PUAN MUDA TENGKU FAUZIAH 1
  • FELCRA LUBUK SIREH 1
  • KG SERI AMAN 1
  • MASJID AL-NUR 1
  • KG BARU 1 PERLIS
  • UNCITI 1
  • KG TITI ULU
  • KG SERI KESIRAI
  • KG SENA DALAM
  • BATU 21 / KOK MAK
  • BATU 20
  • TMN KASTAM 3
  • TMN KASTAM 2
  • SRJK (C) KHOO AIK cp
  • TMN KEMAJUAN
  • TMN SERI MEDAN/TMN CAHAYA
  • JABATAN KESIHATAN NEGERI PERLIS cp
  • SIMPANG TITI CHAI cp
  • PASAR TITI CHAI cp
  • SK UTAN AJI CP
  • SIMPANG LORONG HAMID SAMAH
  • KLINIK DESA KG SURAU cp
  • DEWAN KG UJUNG BATU cp
  • KUARI GUNUNG MEDAN
  • SIMPANG TOK TINA ALUIH cp
  • TMN MEDAN SEPAKAT cp
  • SIMPANG GUNUNG MEDAN cp
  • KG BUKIT KECHIK cp
  • KG ALOR MARUS cp
  • KLINIK DESA BEHOR LATEH cp
  • SK KAYANG cp
  • KG TITI SERONG/PERTUBUHAN PELADANG cp
  • KRAFTANGAN MALAYSIA PERLIS cp
  • KG TELUK BATU 5 cp
  • SIMPANG TIGA PADANG BESAR SELATAN cp
  • WARUNG KAK ETA
  • TMN INDERA INDAH cp
  • BALAI POLIS KUALA PERLIS cp
  • SMK KUALA PERLIS cp
  • KOMPLEKS PERNIAGAAN KUALA PERLIS
  • STESEN BAS KUALA PERLIS cp
  • LKIM cp
  • PANGGUNG WAYANG
  • PLAZA KUALA cp
  • GERAI MAKAN TMN BUKIT KUBU
  • TMN BUKIT KUBU
  • UNIMAP KG WAI
  • SRJK (C) KHAY BENG cp
  • KLINIK DESA SEBERANG RAMAI cp
  • MASJID USMANIAH
  • LADANG BURUNG UNTA PERLIS
  • MASJID JABAL AL-ALA 1
  • BATU 15A PERLIS
  • BATU 15A 1
  • KLINIK KESIHATAN KAKI BUKIT PERLIS cp
  • KPJ KANGAR CP
  • KG BEHOR TEMAK
  • PERTUBUHAN PELADANG
  • SMK SYED ALWI
  • KG BEHOR LATEH
  • KG BEHOR MALI
  • SEK AGAMA AL-ISLAHIYAH
  • KG SG BUGIS
  • BALAI POLIS SIMPANG EMPAT
  • KOMPLEKS SIMPANG EMPAT MPK
  • SIMPANG UNIMAP
  • SHELL SIMPANG EMPAT
  • SG PADANG
  • PERMATANG BONGOR
  • TOK PULAU
  • SIMPANG KUALA SANGLANG / MASJID AL-MAGHFIRAH
  • SMK SANGLANG
  • SIMPANG TIGA SG BARU
  • SK SANGLANG
  • SIMPANG TIGA PADANG KERIA
  • MASJID SIMPANG SANGLANG
  • JALAN SEPAKAT
  • KLINIK KESIHATAN KUALA SANGLANG 1
  • JALAN SEPAKAT 1
  • MASJID SIMPANG SANGLANG 1
  • SIMPANG TIGA PADANG KERIA 1
  • SK SANGLANG 1
  • SIMPANG TIGA SG BARU 1
  • SMK SANGLANG 1
  • SK SANGLANG KEDAH
  • KLINIK DESA SANGLANG KEDAH
  • PEKAN KERPAN
  • SMK AYER ITAM
  • AYER ITAM
  • MEDAN SELERA AYER ITAM
  • PARIT ALOR CHANGILEH
  • SIMPANG SG KOROK
  • KG JERLUN
  • SMK JERLUN
  • KG KELOMPANG
  • MASJID AL-MAHMUDI
  • KG PADANG LALANG
  • PEKAN KECIL KUALA SUNGAI
  • KLINIK KESIHATAN JALAN PUTRA
  • TMN SELAYANG
  • SMKA KEDAH
  • MASJID AL-HIDAYAH
  • SK BEHOR MALI
  • KLINIK KESIHATAN KUALA SANGLANG
  • SJKC CHIN HUN
  • MASJID KG SIMPANG EMPAT KUAR
  • KOMPLEKS PERNIAGAAN ALOR JAGGUS
  • KOMPLEKS PERNIAGAAN MERGONG JAYA
  • TMN RAKYAT
  • DEWAN TMN WIRA
  • TMN PANDAN
  • SG ANAK BUKIT
  • RHB JALAN BADLI SHAH
  • PEKAN RABU
  • TUDM KEPALA BATAS
  • PEKAN KEPALA BATAS
  • TMN JALAI JAYA
  • KEM TOK JALAL
  • SMK TUNKU ANUM TUNKU ABDUL RAHMAN
  • KEM SULTAN ABDUL HALIM MUADZAM SHAH
  • SMK SULTAN ABDUL HALIM
  • TNB TANJUNG SEPAH
  • TANAH MERAH
  • PEJABAT SADA
  • HOTEL PUTRA REGENCY
  • MASJID REPOH ARAU
  • TMN SERI PILIHAN
  • TMN REPOH INDAH/TMN MIDIN INDAH
  • KG KUBANG GAJAH
  • GUAR SANJI
  • TMN JELEMPOK JAYA
  • HUTAN KANDIS
  • KG JELOMPOK
  • SK KUBANG GAJAH
  • MEDAN PEKAN ARAU
  • SEMPADAN PERLIS-KEDAH
  • TMN BAHAGIA 2
  • SK KODIANG
  • KODIANG LAMA
  • KG KANDIS
  • CALTEX
  • KOTA SIPUTEH
  • PADANG SERA
  • BHP PADANG SERA
  • WAT BOONYARAM
  • DEWAN PADANG SERA
  • MADRASAH NADRAH HASANAH
  • MELELE
  • KG PUTAT / KG POCHAN
  • MASJID AL-ISLAH
  • BATU 20 PERLIS
  • SM SAINS KUBANG PASU
  • CALTEX KG IMAM / MASJID KG IMAM
  • BATU 18 PERLIS
  • KILANG PADI JASMINE
  • PADANG PERAHU
  • MASJID PADANG PERAHU
  • SK PADANG PERAHU
  • KG HUTAN SETALI (1)
  • KG HUTAN SETALI (2)
  • MADA
  • JKR BATU 17
  • KLINIK KESIHATAN TUNJANG
  • KG LUBUK
  • KLINIK TUNJANG
  • PEKAN TUNJANG (1)
  • PEKAN TUNJANG (2)
  • SK TUNJANG
  • PEJABAT PENGHULU BKT TUNJANG
  • TMN SERI NYIOR
  • SIMPANG TIGA BEMBAN
  • SMK PULAU NYIOR
  • BATU 14
  • MASJID PULAU KETAM
  • KG MANGGOL
  • BERNAS
  • TMN DESA SINARAN
  • MASJID JITRA
  • PEKAN JITRA
  • TMN SRI CEMPAKA
  • BIRO TATANEGARA KEPALA BATAS
  • SMA TITI BESI
  • TITI GAJAH
  • TMN DESA MUTIARA
  • SK TITI GAJAH
  • KG ALOR SENJAYA
  • and 17 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — up 3.9 since 2026-08-26.

2026-08-06: 63.22026-08-07: 62.72026-08-26: 62.92026-08-27: 66.8
Show the numbers
CheckScoreChange
2026-08-0663.2 first check
2026-08-0762.7 down 0.5
2026-08-2662.9 up 0.2
2026-08-2766.8 up 3.9

What changed since your last check

  • Correctness up 12.0
  • Freshness no change
  • Rider experience up 0.3
  • Realtime quality down 1.9

What changed over time

On 2026-08-06 this feed started at grade D. On 2026-08-27 the check no longer reported: fast travel between far stops (flagged by the MobilityData validator); on some trips the stops fall along the route line in a different order than the schedule lists. As of 2026-08-27 it holds grade D.

A plain-language history of this feed, newest first.

  • 2026-08-27 Score rose 4 points, correctness rose 12 points.

Everything we checked

13 findings, ordered by severity.

Show every finding
  • Warning267 instances

    267 of 267 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

  • Warning256 instances

    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.)

    Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning140 instances

    140 of 140 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

  • Warning108 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

    Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning6 instances

    The feed contains route shapes no trip uses.

    Harmless to riders, but it bloats the feed and suggests stale export data.

    Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)

    Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning2 instances

    Single shape point (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'single_shape_point' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: single_shape_point · See MobilityData GTFS Validator rules

  • Warning2 instances

    2 of 7 sampled vehicle positions were far from their assigned route (worst: 1589 m).

    A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets.

    Fix: Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips. (A vendor support ticket with the trip ids attached.)

    Finding code: scorecard_rt_vehicles_off_route

  • 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

  • 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

  • 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

  • Info232 instances

    About 232 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

    Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices

  • Info2 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.)

    Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

Conformance mark Not yet

One requirement remains for this feed to earn the conformance mark. 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 Met
Service data covers the next 126 days.
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.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks over the last 28 days, with 32s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Live predictions vs schedule

85.7% of reported vehicle positions sat on or near the published route shape.

From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.

Clears the Google and Apple Maps four-week coverage bar. This feed has 125 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

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 70 / 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 85 / 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 24 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 97 / 100
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.

BAS.MY Kangar GTFS data quality grade: D

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/basmy-kangar/2026-08-27.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-27. 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.