@salesforce/plugin-schema
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
Keywords
Versions (showing 100 of 146)
| Version | Deps | Published |
|---|---|---|
| 3.3.130 | 3 / 10 | |
| 3.3.129 | 3 / 10 | |
| 3.3.128 | 3 / 10 | |
| 3.3.127 | 3 / 10 | |
| 3.3.126 | 3 / 10 | |
| 3.3.122 | 3 / 10 | |
| 3.3.121 | 3 / 10 | |
| 3.3.120 | 3 / 10 | |
| 3.3.119 | 3 / 10 | |
| 3.3.118 | 3 / 10 | |
| 3.3.117 | 3 / 10 | |
| 3.3.116 | 3 / 10 | |
| 3.3.115 | 3 / 10 | |
| 3.3.114 | 3 / 10 | |
| 3.3.113 | 3 / 10 | |
| 3.3.112 | 3 / 10 | |
| 3.3.111 | 3 / 10 | |
| 3.3.110 | 3 / 10 | |
| 3.3.109 | 3 / 10 | |
| 3.3.108 | 3 / 10 | |
| 3.3.107 | 3 / 10 | |
| 3.3.106 | 3 / 10 | |
| 3.3.105 | 3 / 10 | |
| 3.3.104 | 3 / 10 | |
| 3.3.103 | 3 / 10 | |
| 3.3.102 | 3 / 10 | |
| 3.3.101 | 3 / 10 | |
| 3.3.100 | 3 / 10 | |
| 3.3.99 | 3 / 10 | |
| 3.3.98 | 3 / 10 | |
| 3.3.97 | 3 / 10 | |
| 3.3.96 | 3 / 10 | |
| 3.3.95 | 3 / 10 | |
| 3.3.94 | 3 / 10 | |
| 3.3.93 | 3 / 10 | |
| 3.3.92 | 3 / 10 | |
| 3.3.91 | 3 / 10 | |
| 3.3.90 | 3 / 10 | |
| 3.3.89 | 3 / 10 | |
| 3.3.88 | 3 / 10 | |
| 3.3.87 | 3 / 10 | |
| 3.3.86 | 3 / 10 | |
| 3.3.85 | 3 / 10 | |
| 3.3.82 | 3 / 10 | |
| 3.3.81 | 3 / 10 | |
| 3.3.80 | 3 / 10 | |
| 3.3.79 | 3 / 10 | |
| 3.3.78 | 3 / 10 | |
| 3.3.77 | 3 / 10 | |
| 3.3.76 | 3 / 10 | |
| 3.3.75 | 3 / 10 | |
| 3.3.74 | 3 / 10 | |
| 3.3.73 | 3 / 10 | |
| 3.3.72 | 3 / 10 | |
| 3.3.71 | 3 / 10 | |
| 3.3.70 | 3 / 10 | |
| 3.3.69 | 3 / 10 | |
| 3.3.68 | 3 / 10 | |
| 3.3.67 | 3 / 10 | |
| 3.3.66 | 3 / 10 | |
| 3.3.65 | 3 / 10 | |
| 3.3.64 | 3 / 10 | |
| 3.3.63 | 3 / 10 | |
| 3.3.62 | 3 / 10 | |
| 3.3.61 | 3 / 10 | |
| 3.3.60 | 3 / 10 | |
| 3.3.59 | 3 / 10 | |
| 3.3.58 | 3 / 10 | |
| 3.3.57 | 3 / 10 | |
| 3.3.56 | 3 / 10 | |
| 3.3.55 | 3 / 10 | |
| 3.3.54 | 3 / 10 | |
| 3.3.53 | 3 / 10 | |
| 3.3.52 | 3 / 10 | |
| 3.3.51 | 3 / 10 | |
| 3.3.50 | 3 / 10 | |
| 3.3.49 | 3 / 10 | |
| 3.3.46 | 3 / 10 | |
| 3.3.45 | 3 / 10 | |
| 3.3.44 | 3 / 10 | |
| 3.3.43 | 3 / 10 | |
| 3.3.42 | 3 / 10 | |
| 3.3.41 | 3 / 10 | |
| 3.3.40 | 3 / 10 | |
| 3.3.39 | 3 / 10 | |
| 3.3.38 | 3 / 10 | |
| 3.3.37 | 3 / 10 | |
| 3.3.36 | 3 / 10 | |
| 3.3.35 | 3 / 10 | |
| 3.3.34 | 3 / 10 | |
| 3.3.33 | 3 / 10 | |
| 3.3.32 | 3 / 10 | |
| 3.3.31 | 3 / 10 | |
| 3.3.30 | 3 / 10 | |
| 3.3.29 | 3 / 10 | |
| 3.3.28 | 3 / 10 | |
| 3.3.27 | 3 / 10 | |
| 3.3.26 | 3 / 10 | |
| 3.3.25 | 3 / 10 | |
| 3.3.24 | 3 / 10 |
v3.3.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.