@swissquote/crafty-preset-react
React tools for crafty
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 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 1.30.2 | 4 / 0 | |
| 1.30.1 | 4 / 0 | |
| 1.30.0 | 4 / 0 | |
| 1.29.0 | 4 / 0 | |
| 1.28.1 | 3 / 0 | |
| 1.28.0 | 3 / 0 | |
| 1.27.0 | 3 / 0 | |
| 1.26.0 | 3 / 0 | |
| 1.25.0 | 3 / 0 | |
| 1.24.0 | 3 / 0 | |
| 1.23.0 | 3 / 0 | |
| 1.22.3 | 3 / 0 | |
| 1.22.2 | 3 / 0 | |
| 1.22.1 | 3 / 0 | |
| 1.22.0 | 3 / 0 | |
| 1.21.1 | 3 / 0 | |
| 1.21.0 | 3 / 0 | |
| 1.20.0 | 3 / 0 | |
| 1.19.1 | 1 / 0 | |
| 1.19.0 | 1 / 0 | |
| 1.18.4 | 1 / 0 | |
| 1.18.3 | 1 / 0 | |
| 1.18.2 | 1 / 0 | |
| 1.18.1 | 1 / 0 | |
| 1.18.0 | 1 / 0 | |
| 1.17.2 | 1 / 0 | |
| 1.17.1 | 1 / 0 | |
| 1.16.3 | 1 / 0 | |
| 1.16.1 | 1 / 0 | |
| 1.16.0 | 1 / 0 | |
| 1.15.0 | 1 / 0 | |
| 1.14.0 | 1 / 0 | |
| 1.13.7 | 1 / 0 | |
| 1.13.5 | 1 / 0 | |
| 1.13.4 | 1 / 0 | |
| 1.13.3 | 1 / 0 | |
| 1.13.2 | 1 / 0 | |
| 1.13.0 | 1 / 0 |
v1.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (stephane.goetz) than the most recent previously approved version (onigoetz) on 2021-03-08, but stephane.goetz is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.