@ilo-org/styles
Styles for products using ILO's Design System
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established ILO org package; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@ilo-org/themes | AI (phantom-deps): Same-org monorepo sibling; declared as CSS/asset dep, not directly imported in JS. | ai | |
| phantom-deps | phantom-dep:@ilo-org/fonts | AI (phantom-deps): CSS/SCSS package; fonts dep is referenced in stylesheets, not JS imports. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@ilo-org/icons | AI (phantom-deps): CSS/SCSS package; icons dep is referenced in stylesheets, not JS imports. Stable false positive. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 1.14.3 | 2 / 9 | |
| 1.14.2 | 2 / 9 | |
| 1.14.1 | 2 / 9 | |
| 1.14.0 | 2 / 9 | |
| 1.13.1 | 2 / 9 | |
| 1.13.0 | 2 / 9 | |
| 1.12.0 | 2 / 9 | |
| 1.11.4 | 2 / 9 | |
| 1.11.3 | 2 / 9 | |
| 1.11.2 | 2 / 9 | |
| 1.11.1 | 2 / 9 | |
| 1.11.0 | 2 / 9 | |
| 1.10.2 | 3 / 9 | |
| 1.10.1 | 3 / 9 | |
| 1.10.0 | 3 / 9 | |
| 1.8.4 | 3 / 9 | |
| 1.8.3 | 3 / 9 | |
| 1.8.2 | 3 / 9 | |
| 1.8.1 | 3 / 9 | |
| 1.8.0 | 3 / 9 | |
| 1.7.3 | 3 / 9 | |
| 1.7.2 | 3 / 9 | |
| 1.7.1 | 3 / 9 | |
| 1.7.0 | 3 / 9 | |
| 1.6.2 | 3 / 9 | |
| 1.6.1 | 3 / 9 | |
| 1.6.0 | 3 / 9 | |
| 1.5.0 | 3 / 9 | |
| 1.4.0 | 3 / 9 | |
| 1.3.4 | 3 / 9 | |
| 1.3.3 | 3 / 9 | |
| 1.3.2 | 3 / 9 | |
| 1.3.1 | 3 / 9 | |
| 1.3.0 | 3 / 9 | |
| 1.2.3 | 3 / 9 | |
| 1.2.2 | 3 / 9 | |
| 1.2.1 | 3 / 9 | |
| 1.2.0 | 3 / 9 | |
| 1.1.1 | 3 / 9 | |
| 1.1.0 | 3 / 9 | |
| 1.0.8 | 3 / 9 | |
| 1.0.7 | 3 / 9 | |
| 1.0.6 | 3 / 9 | |
| 1.0.5 | 3 / 9 |
v1.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.