← Home

@atlaskit/drawer

A drawer is a panel that slides in from the left side of the screen.

27
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@atlaskit/css AI (dependencies): First-party Atlassian Design System sibling package; unvetted status reflects registry gap, not a security concern. ai
dependencies unvetted-dep:@atlaskit/icon AI (dependencies): First-party Atlassian Design System sibling package; unvetted status reflects registry gap, not a security concern. ai
dependencies unvetted-dep:@atlaskit/theme AI (dependencies): First-party Atlassian Design System sibling package; unvetted status reflects registry gap, not a security concern. ai
dependencies unvetted-dep:@atlaskit/button AI (dependencies): First-party Atlassian Design System sibling package; unvetted status reflects registry gap, not a security concern. ai
dependencies unvetted-dep:@atlaskit/motion AI (dependencies): First-party Atlassian Design System sibling package; unvetted status reflects registry gap, not a security concern. ai
dependencies unvetted-dep:@atlaskit/portal AI (dependencies): First-party Atlassian Design System sibling package; unvetted status reflects registry gap, not a security concern. ai
dependencies unvetted-dep:@atlaskit/tokens AI (dependencies): First-party Atlassian Design System sibling package; unvetted status reflects registry gap, not a security concern. ai
dependencies unvetted-dep:@atlaskit/blanket AI (dependencies): First-party Atlassian Design System sibling package; unvetted status reflects registry gap, not a security concern. ai
dependencies unvetted-dep:@atlaskit/analytics-next AI (dependencies): First-party Atlassian Design System sibling package; unvetted status reflects registry gap, not a security concern. ai
phantom-deps phantom-dep:@atlaskit/theme AI (phantom-deps): Same-org package; phantom usage is benign in Atlassian monorepo CSS/token context. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): Same-org package; phantom usage is benign in Atlassian monorepo CSS/token context. ai

Versions (showing 27 of 27)

Version Deps Published
12.1.4 18 / 23
12.1.3 18 / 23
12.1.2 18 / 22
12.1.1 18 / 22
12.1.0 18 / 22
12.0.7 18 / 22
12.0.6 18 / 22
12.0.5 18 / 22
12.0.4 18 / 22
12.0.3 18 / 22
12.0.2 18 / 21
12.0.1 18 / 21
12.0.0 18 / 20
11.0.29 18 / 20
11.0.28 18 / 20
11.0.27 18 / 20
11.0.26 18 / 20
11.0.25 18 / 20
11.0.24 18 / 20
11.0.23 18 / 20
11.0.22 18 / 20
11.0.21 18 / 20
11.0.20 18 / 20
11.0.19 19 / 20
11.0.18 19 / 20
11.0.17 19 / 20
11.0.16 19 / 20

v12.1.4

1 finding
LOW No provenance attestation provenance

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

v12.1.3

1 finding
LOW No provenance attestation provenance

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

v12.1.2

1 finding
LOW No provenance attestation provenance

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

v12.1.1

1 finding
LOW No provenance attestation provenance

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

v12.1.0

1 finding
LOW No provenance attestation provenance

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

v12.0.7

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.

v12.0.6

1 finding
LOW No provenance attestation provenance

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

v12.0.5

1 finding
LOW No provenance attestation provenance

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

v12.0.4

1 finding
LOW No provenance attestation provenance

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

v12.0.3

1 finding
LOW No provenance attestation provenance

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

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

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

v12.0.0

1 finding
LOW No provenance attestation provenance

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

v11.0.29

1 finding
LOW No provenance attestation provenance

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

v11.0.28

1 finding
LOW No provenance attestation provenance

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

v11.0.27

1 finding
LOW No provenance attestation provenance

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

v11.0.26

1 finding
LOW No provenance attestation provenance

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

v11.0.25

1 finding
LOW No provenance attestation provenance

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

v11.0.24

1 finding
LOW No provenance attestation provenance

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

v11.0.23

1 finding
LOW No provenance attestation provenance

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

v11.0.22

1 finding
LOW No provenance attestation provenance

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

v11.0.21

1 finding
LOW No provenance attestation provenance

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

v11.0.20

1 finding
LOW No provenance attestation provenance

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

v11.0.19

1 finding
LOW No provenance attestation provenance

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

v11.0.18

1 finding
LOW No provenance attestation provenance

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

v11.0.17

1 finding
LOW No provenance attestation provenance

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

v11.0.16

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.