@eulerxyz/euler-materials
**Euler Materials** is a component library to help deliver the best experience and drive consistency between Euler web apps.
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 package with 91 versions; lack of provenance is consistent across its history and not a new risk signal. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Declared in config but not directly imported; stable false positive for this UI materials package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.36.0 | 10 / 56 | |
| 1.35.3 | 10 / 56 | |
| 1.35.2 | 10 / 56 | |
| 1.35.1 | 10 / 56 | |
| 1.35.0 | 10 / 56 | |
| 1.34.1 | 10 / 56 | |
| 1.34.0 | 10 / 56 | |
| 1.33.0 | 10 / 56 | |
| 1.32.1 | 10 / 56 | |
| 1.31.1 | 10 / 56 | |
| 1.31.0 | 10 / 56 | |
| 1.30.0 | 10 / 56 | |
| 1.29.2 | 10 / 56 | |
| 1.29.1 | 10 / 56 | |
| 1.29.0 | 10 / 56 | |
| 1.28.2 | 10 / 56 | |
| 1.28.1 | 10 / 56 | |
| 1.27.0 | 10 / 56 | |
| 1.26.0 | 10 / 56 | |
| 1.23.0 | 10 / 56 | |
| 1.22.1 | 10 / 56 | |
| 1.22.0 | 10 / 56 | |
| 1.21.0 | 10 / 56 | |
| 1.20.0 | 10 / 56 | |
| 1.19.0 | 10 / 56 | |
| 1.18.0 | 10 / 56 |
v1.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.