← Home

@trilogy-ds/styles

npm Repository Homepage

<div align='center'>

40
Versions
UNLICENSED
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

bytelravi.khatwanijulienmoexavierbartymaury

Versions (showing 40 of 40)

Version Deps Published
4.18.1 0 / 0
4.17.0 0 / 0
4.16.3 0 / 0
4.16.2 0 / 0
4.13.0 0 / 0
4.12.1 0 / 0
4.12.0 0 / 0
4.11.0 0 / 0
4.10.2 0 / 0
4.10.1 0 / 0
4.10.0 0 / 0
4.9.3 0 / 0
4.9.2 0 / 0
4.9.1 0 / 0
4.9.0 0 / 0
4.8.2 0 / 0
4.8.1 0 / 0
4.8.0 0 / 0
4.7.5 0 / 0
4.7.4 0 / 0
4.7.1 0 / 0
4.7.0 0 / 0
4.6.1 0 / 0
4.6.0 0 / 0
4.5.1 0 / 0
4.5.0 0 / 0
4.4.2 0 / 0
4.4.1 0 / 0
4.4.0 0 / 0
4.3.0 0 / 0
4.2.1 0 / 0
4.1.2 0 / 0
4.1.1 0 / 0
4.1.0 0 / 0
4.0.6 0 / 0
4.0.5 0 / 0
4.0.4 0 / 0
4.0.2 0 / 0
4.0.1 0 / 0
4.0.0 0 / 0

v4.18.1

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: julienmo → GitHub Actions (on 2026-07-23, 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 (julienmo) on 2026-07-23, 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.

v4.4.0

1 finding
LOW No provenance attestation provenance

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

v4.3.0

1 finding
LOW No provenance attestation provenance

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

v4.2.1

1 finding
LOW No provenance attestation provenance

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

v4.1.2

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.6

1 finding
LOW No provenance attestation provenance

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

v4.0.5

1 finding
LOW No provenance attestation provenance

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

v4.0.4

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.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.