@elliemae/ds-legacy-toast
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@xstyled/util | AI (phantom-deps): Likely consumed via bundled dist output; used by styling deps in monorepo. | ai | |
| phantom-deps | phantom-dep:@xstyled/system | AI (phantom-deps): Likely consumed via bundled dist output; used by styling deps in monorepo. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.25 | 7 / 3 | |
| 1.0.24 | 7 / 3 | |
| 1.0.23 | 7 / 3 | |
| 1.0.17 | 7 / 3 | |
| 1.0.16 | 7 / 3 | |
| 1.0.13 | 7 / 3 | |
| 1.0.12 | 7 / 3 | |
| 1.0.11 | 7 / 3 |
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.