About MarinOS

MarinOS is the directory for apps and documentation built by County of Marin teams. Each product links back here from its own MarinOS banner menu.

Building on MarinOS

• marin-app-template — start a new app here
• marin-app-shell — shared navigation, components, and runtime
• marin-ui — design-system styles and tokens used by App Shell
• marin-digital-standards — accessibility, content, brand, and product-design requirements
• marin-skills — AI workflows for building and maintaining Marin applications

Related information

• Status
• Security

Projects

Marin County digital, innovation, transformation projects.

Loading projects…

Accessibility

MarinOS applications target WCAG 2.2 Level AA. We use automated accessibility testing as one part of our accessibility practices.

Accessibility scores

Loading accessibility scores…

Score bands: 90–100 good, 50–89 needs improvement, 0–49 poor.

About the score

Scores come from Google Lighthouse accessibility testing through the PageSpeed Insights API. Scores range from 0–100. Automated testing can identify many accessibility issues, but a score does not determine WCAG conformance. Read how Lighthouse scores accessibility and about the PageSpeed Insights API.

Accessibility standard

County of Marin digital services target WCAG 2.2 Level AA. WCAG provides internationally recognized requirements for making web content accessible to people with disabilities.

Report an issue

If you experience an accessibility problem with a MarinOS application, report the issue so we can review it.

Report an accessibility issue

Tech

MarinOS applications use open technologies and reusable components to deliver County digital services. This page documents the technology, software dependencies, and use of artificial intelligence across MarinOS applications.

Applications and components

Loading technology information…

Dependencies counts software packages and GitHub Actions found by GitHub’s dependency graph. Libraries copied into an application are listed on its own Tech page. AI means AI functionality in the deployed application, not tools used to build it, and is declared by each application’s team.

MarinOS platform

Marin App Shell

The shared runtime every MarinOS application includes: header, footer, routing, and common behavior.

Marin UI

The shared design system behind the shell: styles, components, and brand.

Security

MarinOS applications are designed to be secure by default. Most MarinOS apps are hosted as static websites on GitHub Pages, which means they do not run server-side application code or maintain their own databases.

MarinOS provides common security standards and tools that each application uses. Every application also publishes its own security information so you can see how that specific app handles data and security.

MarinOS security

Loading security information…

GitHub Pages hosting

MarinOS applications hosted on GitHub Pages are static websites. This means:

• Application files are delivered over HTTPS.
• There is no MarinOS application server running behind the website.
• GitHub Pages does not provide a MarinOS application database.
• Browser-based applications can process files and information locally on your device without sending that information to MarinOS.
• Passwords, API keys, private credentials, and other secrets must not be stored in published application code.
• GitHub Pages does not allow applications to configure arbitrary HTTP response headers, so some browser security protections must be implemented within the application itself or are provided by the hosting platform.

If an application connects to an API or another external service, its Security page should describe that connection and what information may be sent.

How it works

MarinOS defines the common security standard. Each application keeps its own security.json file describing its security characteristics. That information is used to generate and validate the application's public security information.

Security by default

• HTTPS
• Content Security Policy
• Browser security protections supported by GitHub Pages and the application
• security.txt
• Dependency monitoring
• Secret scanning
• External resource review
• Application-specific security documentation

Applications

Loading application security inventory…

Report an issue

See security.txt for contact details.

For developers

• Security standard
• Security profiles
• Security schema
• MarinOS's own security.json

Technical information

• security.txt

App status

MarinOS uses Alpha, Beta, and Live to show the maturity of each app. Status helps people understand what to expect when using a MarinOS product.

Alpha

Alpha — Experimental and actively being developed.

Alpha apps are early versions used to explore ideas and test how something might work. Features may be incomplete or change significantly.

• Frequent changes
• Limited testing
• Incomplete functionality
• Experimentation

Beta

Beta — Working and available for real-world testing.

Beta apps have working core functionality and are being tested with real users. Features and workflows may continue to change based on feedback.

• Working core features
• Real-world testing
• Continued improvements
• Occasional limitations

Live

Live — Available for ongoing use.

Live apps are established products available for their intended users. They have stable core functionality and continue to be maintained and improved.

• Stable core functionality
• Ongoing maintenance
• Regular improvements
• Dependable use for the intended purpose

App status

Loading application status inventory…