@spectrum-web-components/table
Web component implementation of a Spectrum design Table
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers consistent with Adobe org team changes; no code or script modifications. | ai | |
| provenance | publisher-changed | AI (provenance): Adobe internal team rotation; new publisher has strong track record (684 approved, 0 rejected). | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/base | AI (dependencies): Same-monorepo sibling dep from Adobe; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/icon | AI (dependencies): Same-monorepo sibling dep from Adobe; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/checkbox | AI (dependencies): Same-monorepo sibling dep from Adobe; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/icons-ui | AI (dependencies): Same-monorepo sibling dep from Adobe; stable pattern across all versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.12.1 | 6 / 0 | |
| 1.12.0 | 6 / 0 | |
| 1.11.2 | 6 / 0 | |
| 1.11.1 | 6 / 0 | |
| 1.11.0 | 6 / 0 | |
| 1.10.0 | 6 / 0 | |
| 1.9.1 | 6 / 0 | |
| 1.9.0 | 6 / 0 | |
| 1.8.0 | 6 / 0 | |
| 1.7.0 | 6 / 0 | |
| 1.6.0 | 6 / 1 |
v1.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.