@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 — the axios compromise (March 2026) relied on exactly this gap.
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 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.99.2 | 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 |
v1.99.2
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 (scoppieters) than the most recent previously approved version (miles.vdw) on 2026-01-28, but scoppieters 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.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
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 (opendocs) than the most recent previously approved version (miles.vdw) on 2026-03-27, but opendocs 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.27.18
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 (scoppieters) than the most recent previously approved version (miles.vdw) on 2026-03-09, but scoppieters 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.27.17
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 (scoppieters) than the most recent previously approved version (miles.vdw) on 2026-03-05, but scoppieters 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.27.16
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 (scoppieters) than the most recent previously approved version (miles.vdw) on 2026-01-28, but scoppieters 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.27.12
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 (scoppieters) than the most recent previously approved version (miles.vdw) on 2026-01-27, but scoppieters 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.26.1
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 (scoppieters) than the most recent previously approved version (miles.vdw) on 2026-01-05, but scoppieters 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.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.13
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 (kharlowsf) on 2025-11-04, 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.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.