Browse the history, then check the record
Ming Official Atlas does not claim to provide a complete annual roster of Ming officials. Its README describes geographic navigation, searches for people and offices, appointment details and sources. The stated scope is 1368 to 1644, with 1566 as the default year and separate desktop and mobile layouts.
For Chinese-reading students, educators and history enthusiasts, those features provide ways to find records by year, place, person or office. The README says the historical material remains under correction and retains source uncertainty. Check a record's cited evidence before relying on it in research or teaching. Our sandbox did not independently verify the historical records.
What the recorded run established
Our run on September 30, 2026, at commit 16d426e recorded installation in 39 seconds and the default build in 22 seconds. Both commands returned exit code 0 without timing out. The matching sandbox record specifies 3 CPUs, 8 GB of memory and the lab-node:22 image.
The build log identifies vinext build and warns that some routes could not be classified through static analysis. It does not show execution of the README's separate npm run build:nas command. The successful default build therefore does not verify the documented virtual-host deployment.
Tests were skipped with the recorded reason "no script". That result does not mean the repository contains no checks. The README lists TypeScript, mobile-component, built-CSS and PHP/MySQL checks that our harness did not execute. Likewise, the scan's missing tests-directory signal describes a directory observation, rather than the absence of validation scripts.
The supplied run contains no browser, mobile-device or deployed-service verification. It does not establish that geographic navigation, year changes, dialogs, administrative login, feedback submission or a live database worked. No new execution was performed for this correction.
Dependency figures and their limits
The stored parser summary records 572 dependency packages and 742 MB. The raw install footer separately reports 567 packages added and 568 audited in 36 seconds. Those counts remain unreconciled. The footer's timing does not replace the harness's 39-second installation measurement, and the parser summary does not establish exhaustive package coverage.
The stored npm audit summary records 14 advisories: 9 high, 4 moderate and 1 low. These are dependency findings, not demonstrated vulnerabilities in the deployed atlas. The supplied record gives neither advisory identities nor exploit paths. Scan coverage is unknown because scannedPackages is absent. Before operating the services, reproduce the audit and determine which findings affect deployed code or build tooling.
Deployment requires a separate check
The README says historical content preferentially reads versioned public snapshots. Analytics, feedback and administration additionally require PHP 8.2, PDO MySQL, MySQL 8.0 and private configuration. Our run did not validate those services.
The deployment guide directs maintainers to upload the contents of dist-nas/ to the website root. Root-relative asset paths currently prevent direct deployment under a domain subdirectory. Private database configuration and sessions sit outside the public website directory. Some historical reconstruction scripts also depend on local source material and database exports absent from the repository.
The guide reports a self-signed certificate at its documented deployment stage and says administrative login and phone-number feedback require valid HTTPS. This is an upstream deployment report, not a fresh observation of the current certificate. Check the present host configuration before enabling those features.
The stored scan identified no Dockerfile, compose file or CI workflow and did not identify a license. These observations apply to the measured checkout. They leave deployment automation and reuse terms unresolved for an adoption decision based on this run.
Alternatives for different tasks
OpenHistoricalMap's website repository documents an editing API. It also provides Docker instructions for local development. Consider it for a map-editing website project. The supplied extract does not establish an equivalent Ming-officials dataset or interface, so it is an infrastructure alternative rather than a ready replacement for this atlas.
Wikimedia's Wikibase RDF Query tools support querying Wikibase instances with RDF. The repository also documents tools for synchronization with a SPARQL-compatible store. Consider them for a Wikibase query workflow. The supplied evidence does not establish equivalent Ming records, coverage or atlas browsing features. Neither alternative was run in our sandbox.
Ratings and unassessed community evidence
The assessed dimensions use a five-point editorial rubric: 1 means major documented obstacles; 2 means substantial unresolved limits; 3 means a workable path with material qualifications; 4 requires broadly verified readiness; and 5 requires comprehensive evidence across the dimension. These judgments are not measured performance or security scores. An unassessed dimension receives no numerical score.
Setup ease is 3/5: installation and the default build succeeded, while the documented deployment requires additional services that our run did not validate. Documentation is 3/5: the supplied Chinese README and deployment guide describe prerequisites, deployment constraints and checks, but our run did not reproduce that operational path. Maturity is 2/5: the measured checkout has no detected CI workflow or license, and our sandbox did not verify deployment. Documented validation scripts do exist.
Community is unassessed. The supplied evidence does not establish dated participation, adoption or maintainer responsiveness, so it cannot support a numerical community judgment.
Before adopting the code, establish reuse terms, reproduce the documented checks relevant to your deployment, review the dependency advisories and verify the browser and service behavior your users will need.

