@uiw/codemirror-themes
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): Publisher changed to GitHub Actions reflects a legitimate CI/CD migration; SLSA provenance attestation confirms automated pipeline publishing for this established uiwjs package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by GitHub Actions publish is consistent with CI/CD migration for a stable, established package; SLSA attestation confirms legitimate pipeline. | ai |
Versions (showing 21 of 121)
| Version | Deps | Published |
|---|---|---|
| 4.12.0 | 3 / 0 | |
| 4.11.6 | 3 / 0 | |
| 4.11.5 | 3 / 0 | |
| 4.11.4 | 3 / 0 | |
| 4.11.3 | 3 / 0 | |
| 4.11.2 | 3 / 0 | |
| 4.11.1 | 3 / 0 | |
| 4.11.0 | 3 / 0 | |
| 4.10.4 | 3 / 0 | |
| 4.10.3 | 3 / 0 | |
| 4.10.2 | 3 / 0 | |
| 4.10.1 | 3 / 0 | |
| 4.10.0 | 3 / 0 | |
| 4.9.6 | 3 / 0 | |
| 4.9.5 | 3 / 0 | |
| 4.9.4 | 3 / 0 | |
| 4.9.3 | 3 / 0 | |
| 4.9.2 | 3 / 0 | |
| 4.9.1 | 3 / 0 | |
| 4.9.0 | 3 / 0 | |
| 4.8.1 | 3 / 0 |
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.