@griffel/jest-serializer
Jest serializer for Griffel
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
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.1.42 | 2 / 0 | |
| 1.1.41 | 2 / 0 | |
| 1.1.40 | 2 / 0 | |
| 1.1.39 | 2 / 0 | |
| 1.1.38 | 2 / 0 | |
| 1.1.37 | 2 / 0 | |
| 1.1.36 | 2 / 0 | |
| 1.1.35 | 2 / 0 | |
| 1.1.34 | 2 / 0 | |
| 1.1.33 | 2 / 0 | |
| 1.1.32 | 2 / 0 | |
| 1.1.31 | 2 / 0 | |
| 1.1.30 | 2 / 0 | |
| 1.1.29 | 2 / 0 | |
| 1.1.28 | 2 / 0 | |
| 1.1.27 | 2 / 0 | |
| 1.1.26 | 2 / 0 | |
| 1.1.25 | 2 / 0 | |
| 1.1.24 | 2 / 0 |
v1.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.