@spectrum-web-components/contextual-help
Web component implementation of a Spectrum design ContextualHelp
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 | publisher-changed | AI (provenance): Adobe SWC monorepo migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern going forward. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a same-org sibling at matching version 1.9.0; consistent with monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/overlay | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; pinned to same version. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/popover | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; pinned to same version. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/base | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; pinned to same version. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/icons-workflow | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; pinned to same version. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/reactive-controllers | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; pinned to same version. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/action-button | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; pinned to same version. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/dialog | AI (dependencies): Sibling package in Adobe's spectrum-web-components monorepo; pinned to same version. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.12.2 | 7 / 0 | |
| 1.12.1 | 7 / 0 | |
| 1.12.0 | 7 / 0 | |
| 1.11.2 | 7 / 0 | |
| 1.11.1 | 7 / 0 | |
| 1.11.0 | 7 / 0 | |
| 1.10.0 | 7 / 0 | |
| 1.9.1 | 7 / 0 | |
| 1.9.0 | 7 / 0 | |
| 1.8.0 | 7 / 0 | |
| 1.7.0 | 6 / 0 | |
| 1.6.0 | 6 / 1 | |
| 1.5.0 | 6 / 1 | |
| 1.4.0 | 6 / 1 | |
| 1.3.0 | 6 / 1 | |
| 1.2.0 | 6 / 1 | |
| 1.1.2 | 6 / 1 | |
| 1.1.1 | 6 / 1 | |
| 1.1.0 | 6 / 1 | |
| 1.0.3 | 6 / 1 | |
| 1.0.2 | 6 / 1 | |
| 1.0.1 | 6 / 1 | |
| 1.0.0 | 6 / 1 |
v1.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.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 (rajrock38) than the most recent previously approved version (rubenc) on 2025-04-15, but rajrock38 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.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.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 (rubenc) than the most recent previously approved version (rajrock38) on 2025-03-13, but rubenc 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.2.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 (rubenc) than the most recent previously approved version (rajrock38) on 2025-02-27, but rubenc 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.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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 (rajrock38) than the most recent previously approved version (rubenc) on 2025-01-29, but rajrock38 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.1.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 (rajrock38) than the most recent previously approved version (rubenc) on 2025-01-29, but rajrock38 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.0.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 (rubenc) than the most recent previously approved version (rajrock38) on 2024-12-09, but rubenc 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.0.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 (pvashish) than the most recent previously approved version (rajrock38) on 2024-11-26, but pvashish 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.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.