@salesforcedevs/dw-components
Lightning web components for https://developer.salesforce.com
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived Salesforce org package; gap likely reflects internal release cadence, not account takeover. | ai | |
| dependencies | unvetted-dep:lodash.orderby | AI (dependencies): lodash.orderby is a well-known utility library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:youtube-player | AI (dependencies): youtube-player is a well-known library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@types/youtube-player | AI (dependencies): @types/youtube-player is a type definitions package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeep | AI (phantom-deps): Declared in dependencies, likely used transitively or via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/youtube-player | AI (phantom-deps): Type-only package loaded by framework convention; not directly imported by design. | ai |
Versions (showing 100 of 158)
| Version | Deps | Published |
|---|---|---|
| 1.99.2 | 7 / 6 | |
| 1.28.3 | 7 / 6 | |
| 1.28.2 | 7 / 6 | |
| 1.28.1 | 7 / 6 | |
| 1.28.0 | 7 / 6 | |
| 1.27.18 | 7 / 6 | |
| 1.27.17 | 7 / 6 | |
| 1.27.16 | 7 / 6 | |
| 1.27.12 | 7 / 6 | |
| 1.26.1 | 7 / 6 | |
| 1.24.0 | 7 / 6 | |
| 1.20.16 | 7 / 6 | |
| 1.20.13 | 7 / 6 | |
| 1.20.5 | 7 / 6 | |
| 1.19.6 | 7 / 6 | |
| 1.18.2 | 7 / 6 | |
| 1.17.8 | 7 / 6 | |
| 1.17.7 | 7 / 6 | |
| 1.15.2 | 7 / 6 | |
| 1.15.0 | 7 / 6 | |
| 1.14.7 | 7 / 6 | |
| 1.14.2 | 7 / 6 | |
| 1.11.0 | 7 / 6 | |
| 1.7.0 | 7 / 6 | |
| 1.6.0 | 7 / 6 | |
| 1.5.0 | 7 / 6 | |
| 1.3.396 | 7 / 6 | |
| 1.3.392 | 7 / 6 | |
| 1.3.391 | 7 / 6 | |
| 1.3.388 | 7 / 6 | |
| 1.3.385 | 7 / 6 | |
| 1.3.384 | 7 / 6 | |
| 1.3.380 | 7 / 6 | |
| 1.3.378 | 7 / 6 | |
| 1.3.377 | 7 / 6 | |
| 1.3.366 | 7 / 6 | |
| 1.3.363 | 7 / 6 | |
| 1.3.362 | 7 / 6 | |
| 1.3.360 | 7 / 6 | |
| 1.3.359 | 7 / 6 | |
| 1.3.349 | 7 / 6 | |
| 1.3.348 | 7 / 6 | |
| 1.3.342 | 7 / 6 | |
| 1.3.341 | 7 / 6 | |
| 1.3.340 | 7 / 6 | |
| 1.3.339 | 7 / 6 | |
| 1.3.338 | 7 / 6 | |
| 1.3.337 | 7 / 6 | |
| 1.3.333 | 7 / 6 | |
| 1.3.324 | 7 / 6 | |
| 1.3.323 | 7 / 6 | |
| 1.3.322 | 7 / 6 | |
| 1.3.316 | 7 / 6 | |
| 1.3.315 | 7 / 6 | |
| 1.3.312 | 7 / 6 | |
| 1.3.311 | 7 / 6 | |
| 1.3.309 | 7 / 6 | |
| 1.3.304 | 7 / 6 | |
| 1.3.302 | 7 / 6 | |
| 1.3.298 | 7 / 6 | |
| 1.3.297 | 7 / 6 | |
| 1.3.294 | 7 / 6 | |
| 1.3.293 | 7 / 6 | |
| 1.3.292 | 7 / 6 | |
| 1.3.291 | 7 / 6 | |
| 1.3.290 | 7 / 6 | |
| 1.3.287 | 7 / 6 | |
| 1.3.285 | 7 / 6 | |
| 1.3.276 | 7 / 6 | |
| 1.3.275 | 7 / 6 | |
| 1.3.265 | 7 / 6 | |
| 1.3.261 | 5 / 6 | |
| 1.3.259 | 5 / 6 | |
| 1.3.256 | 5 / 6 | |
| 1.3.252 | 5 / 6 | |
| 1.3.235 | 5 / 6 | |
| 1.3.227 | 5 / 6 | |
| 1.3.225 | 5 / 6 | |
| 1.3.218 | 5 / 6 | |
| 1.3.214 | 5 / 6 | |
| 1.3.213 | 5 / 6 | |
| 1.3.212 | 5 / 6 | |
| 1.3.211 | 5 / 6 | |
| 1.3.207 | 5 / 6 | |
| 1.3.206 | 5 / 6 | |
| 1.3.196 | 5 / 6 | |
| 1.3.195 | 5 / 6 | |
| 1.3.191 | 5 / 6 | |
| 1.3.189 | 5 / 6 | |
| 1.3.188 | 5 / 6 | |
| 1.3.187 | 5 / 6 | |
| 1.3.185 | 5 / 6 | |
| 1.3.184 | 5 / 6 | |
| 1.3.179 | 5 / 6 | |
| 1.3.175 | 5 / 6 | |
| 1.3.173 | 5 / 6 | |
| 1.3.171 | 5 / 6 | |
| 1.3.170 | 5 / 6 | |
| 1.3.162 | 5 / 6 | |
| 1.3.156 | 5 / 6 |
v1.28.3
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 (miles.vdw) than the most recent previously approved version (dkulan) on 2026-07-10, but miles.vdw is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.396
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.392
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.391
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.388
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.385
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.384
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.380
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.378
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.377
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.366
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.363
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.362
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.360
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.359
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.349
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.348
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.341
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.340
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.339
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.338
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.337
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.333
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 (kharlowsf) than the most recent previously approved version (dkulan) on 2024-09-13, but kharlowsf is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.324
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.323
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.322
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.316
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.315
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.312
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.311
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.309
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.304
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.302
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.298
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.297
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.294
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.293
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.292
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.291
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.290
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.287
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.285
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.276
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 (dkulan) than the most recent previously approved version (miles.vdw) on 2024-06-20, but dkulan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.275
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 (dkulan) than the most recent previously approved version (miles.vdw) on 2024-06-20, but dkulan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.265
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.261
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.259
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.256
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.214
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.213
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.212
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.211
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.207
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.206
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.189
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.187
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.184
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.171
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.170
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.