@spectrum-web-components/bundle
`@spectrum-web-components/bundle` is a master dependency that allows a project to import any and all of the Spectrum Web Components. While it is a great approach to prototyping, the fact that it versions all of the Spectrum Web Components packages collect
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@spectrum-web-components/card | AI (dependencies): Same-org monorepo sibling; expected for this bundle package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/breadcrumbs | AI (dependencies): Same-org monorepo sibling; expected for this bundle package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/action-menu | AI (dependencies): Same-org monorepo sibling; expected for this bundle package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/action-bar | AI (dependencies): Same-org monorepo sibling; expected for this bundle package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/combobox | AI (dependencies): Same-org monorepo sibling; expected for this bundle package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/radio | AI (dependencies): Same-org monorepo sibling; expected for this bundle package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/icons | AI (dependencies): Same-org monorepo sibling; expected for this bundle package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/tags | AI (dependencies): Same-org monorepo sibling; expected for this bundle package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/link | AI (dependencies): Same-org monorepo sibling; expected for this bundle package. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/grid | AI (dependencies): Same-org monorepo sibling; expected for this bundle package. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/truncated | AI (phantom-deps): Bundle package declares same-org deps for re-export; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/base | AI (phantom-deps): Bundle package re-exports siblings; direct imports not expected in bundle entry. | ai | |
| provenance | no-provenance | AI (provenance): Adobe monorepo; provenance absence is common and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/reactive-controllers | AI (phantom-deps): Bundle package re-exports siblings; direct imports not expected in bundle entry. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/infield-button | AI (phantom-deps): Bundle package re-exports siblings; direct imports not expected in bundle entry. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/close-button | AI (phantom-deps): Bundle package re-exports siblings; direct imports not expected in bundle entry. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/clear-button | AI (phantom-deps): Bundle package re-exports siblings; direct imports not expected in bundle entry. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/iconset | AI (phantom-deps): Bundle package re-exports siblings; direct imports not expected in bundle entry. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/styles | AI (phantom-deps): Bundle package re-exports siblings; direct imports not expected in bundle entry. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/shared | AI (phantom-deps): Bundle package re-exports siblings; direct imports not expected in bundle entry. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/modal | AI (phantom-deps): Bundle package re-exports siblings; direct imports not expected in bundle entry. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/grid | AI (phantom-deps): Bundle package re-exports siblings; direct imports not expected in bundle entry. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.12.2 | 74 / 0 | |
| 1.12.1 | 74 / 0 | |
| 1.12.0 | 74 / 0 | |
| 1.11.2 | 74 / 0 | |
| 1.10.0 | 74 / 0 | |
| 1.9.0 | 74 / 0 | |
| 1.8.0 | 74 / 0 | |
| 1.7.0 | 74 / 0 | |
| 1.6.0 | 74 / 0 | |
| 1.5.0 | 74 / 0 | |
| 1.4.0 | 74 / 0 | |
| 1.3.0 | 74 / 0 | |
| 1.2.0 | 74 / 0 | |
| 1.1.2 | 74 / 0 | |
| 1.1.1 | 74 / 0 | |
| 1.0.3 | 74 / 0 | |
| 1.0.2 | 74 / 0 | |
| 1.0.1 | 74 / 0 | |
| 1.0.0 | 74 / 0 |
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 findings[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findings[Accepted risk] Package 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 findings[Accepted risk] Package 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
2 findings[Accepted risk] Package 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-02-12, 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.1
2 findings[Accepted risk] Package 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 findings[Accepted risk] Package 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 (pvashish) 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 findings[Accepted risk] Package 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 (rubenc) 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
2 findings[Accepted risk] Package 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 2024-11-11, 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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.