@junipero/transitions
🏔 Junipero Design System React Transitions
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 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 3.13.0 | 0 / 1 | |
| 3.12.22 | 0 / 1 | |
| 3.12.20 | 0 / 1 | |
| 3.12.19 | 0 / 1 | |
| 3.12.18 | 0 / 1 | |
| 3.12.17 | 0 / 1 | |
| 3.12.16 | 0 / 1 | |
| 3.12.15 | 0 / 1 | |
| 3.12.14 | 0 / 1 | |
| 3.12.13 | 0 / 1 | |
| 3.12.12 | 0 / 1 | |
| 3.12.11 | 0 / 1 | |
| 3.12.10 | 0 / 1 | |
| 3.12.9 | 0 / 1 | |
| 3.12.8 | 0 / 1 | |
| 3.12.7 | 0 / 1 | |
| 3.12.6 | 0 / 1 | |
| 3.12.5 | 0 / 1 | |
| 3.12.4 | 0 / 1 | |
| 3.12.3 | 0 / 1 | |
| 3.12.1 | 0 / 1 | |
| 3.12.0 | 0 / 1 | |
| 3.11.0 | 0 / 1 | |
| 3.10.7 | 0 / 1 | |
| 3.10.6 | 0 / 1 | |
| 3.10.5 | 0 / 1 | |
| 3.10.4 | 0 / 1 | |
| 3.10.3 | 0 / 1 | |
| 3.10.1 | 0 / 1 | |
| 3.10.0 | 0 / 1 | |
| 3.9.1 | 0 / 1 | |
| 3.9.0 | 0 / 1 | |
| 3.8.1 | 0 / 1 | |
| 3.8.0 | 0 / 1 | |
| 3.7.4 | 0 / 1 | |
| 3.7.3 | 0 / 1 | |
| 3.7.2 | 0 / 1 | |
| 3.7.1 | 0 / 1 | |
| 3.7.0 | 0 / 1 | |
| 3.6.3 | 0 / 1 | |
| 3.6.2 | 0 / 1 | |
| 3.6.1 | 0 / 1 | |
| 3.6.0 | 0 / 1 | |
| 3.5.5 | 0 / 1 | |
| 3.5.4 | 0 / 1 | |
| 3.5.3 | 0 / 1 | |
| 3.5.2 | 0 / 1 | |
| 3.5.1 | 0 / 1 | |
| 3.5.0 | 0 / 1 | |
| 3.4.11 | 2 / 0 | |
| 3.4.1 | 2 / 0 |
v3.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.