@jayree/sfdx-plugin-legacy
A Salesforce CLI plugin containing all jayree legacy commands.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Publisher consistently publishes without provenance; stable pattern across 178 versions. | ai | |
| dependencies | unvetted-dep:@jayree/changelog | AI (dependencies): Same-author namespace dependency; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai |
Versions (showing 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 1.1.182 | 12 / 44 | |
| 1.1.181 | 12 / 44 | |
| 1.1.180 | 12 / 44 | |
| 1.1.179 | 12 / 44 | |
| 1.1.178 | 12 / 44 | |
| 1.1.177 | 12 / 44 | |
| 1.1.176 | 12 / 44 | |
| 1.1.175 | 12 / 44 | |
| 1.1.174 | 12 / 44 | |
| 1.1.173 | 12 / 44 | |
| 1.1.171 | 12 / 44 | |
| 1.1.170 | 12 / 44 | |
| 1.1.168 | 12 / 44 | |
| 1.1.167 | 12 / 44 | |
| 1.1.166 | 12 / 44 | |
| 1.1.165 | 12 / 44 | |
| 1.1.164 | 12 / 44 | |
| 1.1.163 | 12 / 44 | |
| 1.1.162 | 12 / 44 | |
| 1.1.161 | 12 / 44 | |
| 1.1.160 | 12 / 44 | |
| 1.1.159 | 12 / 44 | |
| 1.1.158 | 12 / 44 | |
| 1.1.157 | 12 / 44 | |
| 1.1.156 | 12 / 44 | |
| 1.1.155 | 12 / 44 | |
| 1.1.154 | 12 / 44 | |
| 1.1.153 | 12 / 44 | |
| 1.1.152 | 12 / 44 | |
| 1.1.151 | 12 / 44 | |
| 1.1.150 | 12 / 44 | |
| 1.1.149 | 12 / 44 | |
| 1.1.148 | 12 / 44 | |
| 1.1.147 | 12 / 44 | |
| 1.1.146 | 12 / 44 | |
| 1.1.145 | 12 / 44 | |
| 1.1.144 | 12 / 44 | |
| 1.1.143 | 12 / 44 | |
| 1.1.142 | 12 / 44 | |
| 1.1.141 | 12 / 44 | |
| 1.1.140 | 12 / 44 | |
| 1.1.139 | 12 / 44 | |
| 1.1.138 | 12 / 44 | |
| 1.1.137 | 12 / 44 | |
| 1.1.136 | 12 / 44 | |
| 1.1.135 | 12 / 44 | |
| 1.1.134 | 12 / 44 | |
| 1.1.133 | 12 / 44 | |
| 1.1.132 | 12 / 44 | |
| 1.1.131 | 12 / 44 | |
| 1.1.130 | 12 / 44 | |
| 1.1.129 | 12 / 44 | |
| 1.1.128 | 12 / 44 | |
| 1.1.127 | 12 / 44 | |
| 1.1.126 | 12 / 44 | |
| 1.1.125 | 12 / 44 | |
| 1.1.124 | 12 / 44 | |
| 1.1.123 | 12 / 44 | |
| 1.1.122 | 12 / 44 | |
| 1.1.121 | 12 / 44 | |
| 1.1.120 | 12 / 44 | |
| 1.1.119 | 12 / 44 | |
| 1.1.118 | 12 / 44 | |
| 1.1.117 | 12 / 44 | |
| 1.1.116 | 12 / 44 | |
| 1.1.115 | 12 / 44 | |
| 1.1.114 | 12 / 44 | |
| 1.1.113 | 12 / 44 | |
| 1.1.112 | 12 / 44 | |
| 1.1.111 | 12 / 44 | |
| 1.1.110 | 12 / 44 | |
| 1.1.109 | 12 / 44 | |
| 1.1.108 | 12 / 44 | |
| 1.1.107 | 12 / 44 | |
| 1.1.106 | 12 / 44 | |
| 1.1.105 | 12 / 44 | |
| 1.1.104 | 12 / 44 | |
| 1.1.103 | 12 / 44 | |
| 1.1.102 | 12 / 44 | |
| 1.1.101 | 12 / 44 | |
| 1.1.100 | 12 / 44 | |
| 1.1.99 | 12 / 44 | |
| 1.1.98 | 12 / 44 | |
| 1.1.97 | 12 / 44 | |
| 1.1.96 | 12 / 44 | |
| 1.1.95 | 12 / 44 | |
| 1.1.94 | 12 / 44 | |
| 1.1.93 | 12 / 44 | |
| 1.1.92 | 12 / 44 | |
| 1.1.91 | 12 / 44 | |
| 1.1.90 | 12 / 44 | |
| 1.1.89 | 12 / 44 | |
| 1.1.88 | 12 / 44 | |
| 1.1.87 | 12 / 44 | |
| 1.1.86 | 12 / 44 |
v1.1.182
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.181
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.180
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.179
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.