← Home

@spectrum-web-components/asset

npm Repository Homepage

Use an `<sp-asset>` element to visually represent a file, folder or image in your application. File and folder representations will center themselves horizontally and vertically in the space provided to the element. Images will be contained to the element

8
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation 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
dependencies unvetted-dep:@spectrum-web-components/base AI (dependencies): Same Adobe monorepo sibling dependency; stable pattern across all versions of this package family. ai
provenance no-provenance AI (provenance): Adobe's Spectrum WC monorepo consistently publishes without Sigstore provenance; stable pattern across all versions. ai

Versions (showing 8 of 8)

Version Deps Published
1.11.2 2 / 0
1.11.1 2 / 0
1.11.0 2 / 0
1.10.0 2 / 0
1.9.1 1 / 0
1.8.0 1 / 0
1.7.0 1 / 0
1.6.0 1 / 1

v1.11.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.11.1

1 finding
INFO No provenance attestation provenance

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

v1.11.0

1 finding
INFO No provenance attestation provenance

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

v1.10.0

1 finding
INFO No provenance attestation provenance

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

v1.9.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.

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.0

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.6.0

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.