@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 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 |
v3.3.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.