@uwdata/mosaic-inputs
Mosaic input components.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jheer is the named package author (Jeffrey Heer, UW IDL); transition from domoritz is expected for this org package. | ai | |
| provenance | no-provenance | AI (provenance): Established @uwdata monorepo package; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.29.2 | 2 / 0 | |
| 0.29.1 | 2 / 0 | |
| 0.29.0 | 2 / 0 | |
| 0.28.1 | 2 / 0 | |
| 0.28.0 | 2 / 0 | |
| 0.27.0 | 2 / 0 | |
| 0.26.0 | 2 / 0 | |
| 0.25.0 | 2 / 0 | |
| 0.24.4 | 2 / 0 | |
| 0.24.3 | 2 / 0 | |
| 0.24.2 | 2 / 0 | |
| 0.24.1 | 2 / 0 | |
| 0.24.0 | 2 / 0 | |
| 0.23.1 | 2 / 0 | |
| 0.23.0 | 2 / 0 | |
| 0.22.0 | 2 / 0 | |
| 0.21.1 | 2 / 0 | |
| 0.21.0 | 2 / 0 | |
| 0.20.1 | 2 / 0 | |
| 0.20.0 | 2 / 0 | |
| 0.19.1 | 2 / 0 | |
| 0.19.0 | 2 / 0 | |
| 0.18.0 | 2 / 0 | |
| 0.17.0 | 2 / 0 | |
| 0.16.2 | 2 / 0 | |
| 0.16.1 | 2 / 0 | |
| 0.15.0 | 3 / 0 | |
| 0.14.1 | 3 / 0 | |
| 0.14.0 | 3 / 0 | |
| 0.13.0 | 3 / 0 | |
| 0.12.2 | 3 / 0 | |
| 0.12.1 | 3 / 0 | |
| 0.12.0 | 3 / 0 | |
| 0.11.0 | 3 / 0 | |
| 0.10.0 | 3 / 0 | |
| 0.9.0 | 3 / 0 | |
| 0.8.0 | 3 / 0 |
v0.29.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.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.