← Home

@atlaskit/blanket

npm Repository Homepage

A blanket covers the underlying UI for a layered component, such as a modal dialog or a tooltip.

32
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

atlassianartifactteam

Keywords

atlaskitreactui

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@atlaskit/css AI (phantom-deps): Same-org @atlaskit scoped dep; phantom usage is consistent with Atlaskit's build/CSS tooling patterns across all versions. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): Same-org @atlaskit scoped dep; phantom usage is consistent with Atlaskit's design token system used indirectly via CSS/build tooling. ai

Versions (showing 32 of 32)

Version Deps Published
16.0.0 7 / 23
15.0.34 7 / 23
15.0.33 7 / 23
15.0.32 7 / 22
15.0.31 7 / 22
15.0.30 7 / 22
15.0.29 7 / 22
15.0.28 7 / 21
15.0.27 7 / 21
15.0.26 7 / 20
15.0.25 7 / 20
15.0.24 7 / 20
15.0.23 7 / 20
15.0.22 7 / 20
15.0.21 7 / 20
15.0.20 7 / 20
15.0.19 8 / 20
15.0.18 8 / 20
15.0.17 8 / 20
15.0.16 8 / 20
15.0.15 8 / 20
15.0.14 8 / 20
15.0.13 8 / 20
15.0.12 8 / 20
15.0.11 8 / 20
15.0.10 8 / 20
15.0.9 8 / 22
15.0.8 8 / 22
15.0.7 8 / 22
15.0.6 8 / 22
15.0.5 8 / 22
15.0.4 8 / 22

v16.0.0

1 finding
LOW No provenance attestation provenance

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

v15.0.34

1 finding
LOW No provenance attestation provenance

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

v15.0.33

1 finding
LOW No provenance attestation provenance

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

v15.0.32

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.

v15.0.31

1 finding
LOW No provenance attestation provenance

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

v15.0.30

1 finding
LOW No provenance attestation provenance

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

v15.0.29

1 finding
LOW No provenance attestation provenance

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

v15.0.28

1 finding
LOW No provenance attestation provenance

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

v15.0.27

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.