@salesforce/plugin-limits
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): salesforce-admin addition reflects Salesforce's consolidation of CLI plugin maintenance under a centralized account; consistent with org-wide pattern across Salesforce packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Mass removal of individual Salesforce developer accounts in favor of centralized salesforce-admin/salesforce-releases is a known Salesforce org maintenance pattern, not a takeover signal. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 193 versions and is actively maintained by salesforce-releases (1131 approved packages); dormancy signal is inconsistent with the overall publish history and likely a data artifact. | ai |
Versions (showing 100 of 132)
| Version | Deps | Published |
|---|---|---|
| 3.3.105 | 2 / 11 | |
| 3.3.104 | 2 / 11 | |
| 3.3.103 | 2 / 11 | |
| 3.3.102 | 2 / 11 | |
| 3.3.101 | 2 / 11 | |
| 3.3.100 | 2 / 11 | |
| 3.3.99 | 2 / 11 | |
| 3.3.98 | 2 / 11 | |
| 3.3.96 | 2 / 11 | |
| 3.3.95 | 2 / 11 | |
| 3.3.94 | 2 / 11 | |
| 3.3.93 | 2 / 11 | |
| 3.3.92 | 2 / 11 | |
| 3.3.91 | 2 / 11 | |
| 3.3.90 | 2 / 11 | |
| 3.3.89 | 2 / 11 | |
| 3.3.88 | 2 / 11 | |
| 3.3.87 | 2 / 11 | |
| 3.3.86 | 2 / 11 | |
| 3.3.85 | 2 / 11 | |
| 3.3.84 | 2 / 11 | |
| 3.3.83 | 2 / 11 | |
| 3.3.82 | 2 / 11 | |
| 3.3.81 | 2 / 11 | |
| 3.3.80 | 2 / 11 | |
| 3.3.79 | 2 / 11 | |
| 3.3.78 | 2 / 11 | |
| 3.3.77 | 2 / 11 | |
| 3.3.76 | 2 / 11 | |
| 3.3.75 | 2 / 11 | |
| 3.3.74 | 2 / 11 | |
| 3.3.73 | 2 / 11 | |
| 3.3.72 | 2 / 11 | |
| 3.3.71 | 2 / 11 | |
| 3.3.70 | 2 / 11 | |
| 3.3.69 | 2 / 11 | |
| 3.3.67 | 2 / 11 | |
| 3.3.66 | 2 / 11 | |
| 3.3.65 | 2 / 11 | |
| 3.3.64 | 2 / 11 | |
| 3.3.63 | 2 / 11 | |
| 3.3.62 | 2 / 11 | |
| 3.3.61 | 2 / 11 | |
| 3.3.60 | 2 / 11 | |
| 3.3.59 | 2 / 11 | |
| 3.3.58 | 2 / 11 | |
| 3.3.57 | 2 / 11 | |
| 3.3.56 | 2 / 11 | |
| 3.3.55 | 2 / 11 | |
| 3.3.54 | 2 / 11 | |
| 3.3.53 | 2 / 11 | |
| 3.3.52 | 2 / 11 | |
| 3.3.51 | 2 / 11 | |
| 3.3.50 | 2 / 11 | |
| 3.3.49 | 2 / 11 | |
| 3.3.48 | 2 / 11 | |
| 3.3.47 | 2 / 11 | |
| 3.3.46 | 2 / 11 | |
| 3.3.45 | 2 / 11 | |
| 3.3.44 | 2 / 11 | |
| 3.3.43 | 2 / 11 | |
| 3.3.42 | 2 / 11 | |
| 3.3.41 | 2 / 11 | |
| 3.3.40 | 2 / 11 | |
| 3.3.39 | 2 / 11 | |
| 3.3.38 | 2 / 11 | |
| 3.3.37 | 2 / 11 | |
| 3.3.36 | 2 / 11 | |
| 3.3.35 | 2 / 11 | |
| 3.3.34 | 2 / 11 | |
| 3.3.33 | 2 / 11 | |
| 3.3.32 | 2 / 11 | |
| 3.3.31 | 2 / 11 | |
| 3.3.30 | 2 / 11 | |
| 3.3.29 | 2 / 11 | |
| 3.3.28 | 2 / 11 | |
| 3.3.27 | 2 / 11 | |
| 3.3.26 | 2 / 11 | |
| 3.3.25 | 2 / 11 | |
| 3.3.24 | 2 / 11 | |
| 3.3.23 | 2 / 11 | |
| 3.3.22 | 2 / 11 | |
| 3.3.21 | 2 / 11 | |
| 3.3.20 | 2 / 11 | |
| 3.3.19 | 2 / 11 | |
| 3.3.18 | 2 / 11 | |
| 3.3.17 | 2 / 11 | |
| 3.3.16 | 2 / 11 | |
| 3.3.15 | 2 / 11 | |
| 3.3.14 | 4 / 10 | |
| 3.3.13 | 4 / 10 | |
| 3.3.12 | 4 / 10 | |
| 3.3.11 | 4 / 10 | |
| 3.3.10 | 4 / 10 | |
| 3.3.9 | 4 / 10 | |
| 3.3.8 | 4 / 10 | |
| 3.3.7 | 4 / 10 | |
| 3.3.6 | 4 / 10 | |
| 3.3.5 | 4 / 10 | |
| 3.3.4 | 4 / 10 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.