← Home

@spectrum-web-components/card

npm Repository Homepage

An `<sp-card>` represents a rectangular card that contains a variety of text and image layouts. Cards are typically used to encapsulate units of a data set, such as a gallery of image/caption pairs.

15
Versions
Apache-2.0
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

caseyisonittaratadoberajrock38jnjoshnikkimkrubencjianliao79pvashishpatrickfulton

Keywords

design-systemspectrumadobeadobe-spectrumweb componentsweb-componentslit-elementlit-htmlcomponentcss

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): Adobe Spectrum UI component; name similarity to 'cors' is purely coincidental for a scoped @spectrum-web-components package. ai
phantom-deps phantom-dep:@spectrum-web-components/styles AI (phantom-deps): Same-org sibling dep; CSS-only package likely consumed via side-effects, not direct import. ai
phantom-deps phantom-dep:@spectrum-web-components/icons-workflow AI (phantom-deps): Same-org sibling dep; icons may be referenced indirectly via templates/HTML, not ES imports. ai

Versions (showing 15 of 15)

Version Deps Published
1.12.2 8 / 0
1.12.1 8 / 0
1.12.0 8 / 0
1.11.2 8 / 0
1.11.1 8 / 0
1.11.0 8 / 0
1.10.0 8 / 0
1.9.1 8 / 0
1.9.0 8 / 0
1.8.0 8 / 0
1.7.0 8 / 0
1.6.0 7 / 1
1.1.0 7 / 1
1.0.2 7 / 1
1.0.1 7 / 1

v1.12.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pvashish → rajrock38 (on 2025-01-29, known maintainer) provenance

This version was published by a different npm account (rajrock38) than the most recent previously approved version (pvashish) 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.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.