← Home

@ongov/ontario-design-system-complete-styles

npm Repository Homepage

Complete styles package for the Ontario Design System containing all SASS and CSS for use independently of the Component Library.

4
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ods-devopsmstjeansmorrisnicholasgajewskikylebinger

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@ongov/ontario-design-system-design-tokens AI (phantom-deps): Same-org CSS/SASS bundle; deps are re-exported assets, not JS imports. Stable false positive. ai
phantom-deps phantom-dep:@ongov/ontario-design-system-global-styles AI (phantom-deps): Same-org CSS/SASS bundle; deps are re-exported assets, not JS imports. Stable false positive. ai
phantom-deps phantom-dep:@ongov/ontario-design-system-component-library AI (phantom-deps): Same-org CSS/SASS bundle; deps are re-exported assets, not JS imports. Stable false positive. ai

Versions (showing 4 of 4)

Version Deps Published
9.0.0 3 / 11
8.0.0 3 / 11
7.0.0 3 / 11
6.0.0 3 / 11

v9.0.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: smorris → GitHub Actions (on 2026-07-27, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (smorris) on 2026-07-27, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v7.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.