@spectrum-css/table
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate Adobe team maintainer transition on an official monorepo package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Normal Adobe org maintainer rotation, no behavioral compromise signal. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with team handoff within Adobe org. | ai | |
| source-diff | source-size-tripled | AI (source-diff): CSS component dist growth, not a payload; no executable risk found. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 8.2.0 | 0 / 5 | |
| 8.1.1 | 0 / 5 | |
| 8.1.0 | 0 / 5 | |
| 8.0.1 | 0 / 9 | |
| 8.0.0 | 0 / 9 | |
| 3.0.1 | 0 / 5 |
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-02-12. It has since remained available on npm for 520 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-02-04. It has since remained available on npm for 528 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-01-31. It has since remained available on npm for 532 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.