Official legislation, gazettes, tax-authority guidance, schemas, APIs, and repositories.
Methodology · 2026-07-31.2
How the evidence works.
TaxOSS is a discovery and research index. It separates repository telemetry, legal research, production evidence, and maintainer control so one signal cannot masquerade as another.
Inclusion and exclusion
A listing must be a public source repository or Hugging Face artifact, have a discoverable open license, and make tax, fiscal reporting, or tax-policy work a primary purpose. General accounting products, thin clients for closed commercial services, unlicensed code, and archived repositories are not newly indexed. Existing projects that later become archived remain as historical records and are excluded from active signals.
Source hierarchy
Project-controlled evidence
Repository files, releases, documentation, security policies, test suites, and verified maintainer statements.
Independent secondary evidence
Used for context or corroboration, never to silently override a primary source.
Four separate signal classes
Repository activityAutomatedLast push, archive state, and source-fetch time. Activity does not establish legal currency.
Legal currencyEditorialJurisdiction and scope-specific assessment with an as-of date and supporting sources.
Production readinessEvidence-basedExperimental, pilot, or production evidence. Popularity and authority authorship are not substitutes.
Maintainer provenanceAttributedWho publishes the code and how control was verified. This is not certification.
Review and freshness
Publishing a mandate or project evaluation records the reviewer, date, evidence, and next review due date. Editing a draft does not renew the review. Overdue means the TaxOSS review needs refreshing; it does not mean the law expired or the software became invalid. Missing assessment is shown as Not reviewed, never inferred as a failure.
Enterprise rubric
Documentation, tests, release discipline, security process, deployment operability, data handling, governance continuity, and support path are assessed separately. TaxOSS does not calculate a composite score because priorities and controls vary by use case.
Private workspace semantics
The Workspace heatmap intersects the jurisdictions, tax domains, and Process selected by the member. Gap means the public TaxOSS index has no matching non-archived project; candidate counts show discoverable projects, not suitability or compliance. Candidate, Evaluating, Pilot, Adopted, and Not a fit are private member-entered decision states, not TaxOSS endorsements. CSV exports are point-in-time records carrying their UTC generation time, evidence dates, source links, and this methodology version.
Conflicts, corrections, and limitations
Conflicting license or scope evidence is labeled rather than resolved by assumption. Maintainers may correct descriptive project data, but only site administrators publish legal and readiness assessments. TaxOSS does not audit dependencies, certify software, provide legal advice, promise completeness, or replace security, tax, procurement, and implementation review by the adopting organization.
Report a correction to pascal@lurn.digital.