@ilo-org/styles Apache-2.0 16 versions

@ilo-org/styles

npm Repository Homepage

Styles for products using ILO's Design System

16

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

decentworkdrodinis

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	2026/05/31
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	2026/05/19
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	2026/05/16
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	2026/05/16

Versions (showing 16 of 16)

Version	Deps	Published
1.13.1	2 / 9	2026-05-25
1.13.0	2 / 9	2026-05-21
1.12.0	2 / 9	2026-03-23
1.11.4	2 / 9	2026-02-19
1.11.3	2 / 9	2026-01-21
1.11.2	2 / 9	2026-01-18
1.11.1	2 / 9	2026-01-15
1.11.0	2 / 9	2025-12-12
1.10.2	3 / 9	2025-12-01
1.10.1	3 / 9	2025-11-25
1.10.0	3 / 9	2025-10-26
1.8.4	3 / 9	2025-05-30
1.8.3	3 / 9	2025-05-29
1.8.2	3 / 9	2025-05-27
1.8.1	3 / 9	2025-05-22
1.8.0	3 / 9	2025-05-12

v1.13.1

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.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.

v1.11.4

1 finding

LOW No provenance attestation provenance

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

v1.11.3

1 finding

LOW No provenance attestation provenance

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

v1.11.2

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.

v1.11.1

1 finding

LOW No provenance attestation provenance

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

v1.11.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.

v1.10.2

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.

v1.10.1

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.

v1.10.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.

v1.8.4

1 finding

LOW No provenance attestation provenance

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

v1.8.3

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.

v1.8.2

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.

v1.8.1

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.

v1.8.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.