← Home

@atlaskit/calendar

npm Repository Homepage
43
Versions
—
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): Same-org @atlaskit scoped dependency; legitimate internal Atlassian UI toolkit dep, not a security risk. ai
dependencies unvetted-dep:@atlaskit/icon AI (dependencies): Same-org @atlaskit scoped dependency; legitimate internal Atlassian UI toolkit dep, not a security risk. ai
dependencies unvetted-dep:@atlaskit/button AI (dependencies): Same-org @atlaskit scoped dependency; legitimate internal Atlassian UI toolkit dep, not a security risk. ai
dependencies unvetted-dep:@atlaskit/locale AI (dependencies): Same-org @atlaskit scoped dependency; legitimate internal Atlassian UI toolkit dep, not a security risk. ai
dependencies unvetted-dep:@atlaskit/tokens AI (dependencies): Same-org @atlaskit scoped dependency; legitimate internal Atlassian UI toolkit dep, not a security risk. ai
dependencies unvetted-dep:@atlaskit/heading AI (dependencies): Same-org @atlaskit scoped dependency; legitimate internal Atlassian UI toolkit dep, not a security risk. ai
dependencies unvetted-dep:@atlaskit/primitives AI (dependencies): Same-org @atlaskit scoped dependency; legitimate internal Atlassian UI toolkit dep, not a security risk. ai
dependencies unvetted-dep:@atlaskit/analytics-next AI (dependencies): Same-org @atlaskit scoped dependency; legitimate internal Atlassian UI toolkit dep, not a security risk. ai
dependencies unvetted-dep:@atlaskit/platform-feature-flags AI (dependencies): Same-org @atlaskit scoped dependency; legitimate internal Atlassian UI toolkit dep, not a security risk. ai
phantom-deps phantom-dep:@atlaskit/css AI (phantom-deps): Same-org phantom dep in Atlaskit monorepo; used indirectly via CSS compilation pipeline, not a security concern. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): Same-org phantom dep in Atlaskit monorepo; used indirectly via design token system, not a security concern. ai
provenance no-provenance AI (provenance): Established Atlassian package (3371 days, 296 versions) published by verified atlassianartifactteam; lack of Sigstore provenance is not a risk signal here. ai

Versions (showing 43 of 43)

Version Deps Published
17.2.20 13 / 15
17.2.19 13 / 15
17.2.18 13 / 15
17.2.17 13 / 15
17.2.16 13 / 14
17.2.15 13 / 14
17.2.14 13 / 14
17.2.13 14 / 14
17.2.12 14 / 14
17.2.11 14 / 13
17.2.10 14 / 13
17.2.9 14 / 13
17.2.8 14 / 13
17.2.7 14 / 13
17.2.6 14 / 13
17.2.5 14 / 13
17.2.4 14 / 13
17.2.3 14 / 13
17.2.2 14 / 13
17.2.1 14 / 13
17.2.0 14 / 13
17.1.27 13 / 15
17.1.26 13 / 15
17.1.25 13 / 15
17.1.24 13 / 15
17.1.23 13 / 15
17.1.22 13 / 15
17.1.21 13 / 15
17.1.20 13 / 15
17.1.19 13 / 15
17.1.18 13 / 15
17.1.17 13 / 15
17.1.16 13 / 15
17.1.15 13 / 15
17.1.14 13 / 16
17.1.13 13 / 17
17.1.12 13 / 17
17.1.11 13 / 17
17.1.10 13 / 17
17.1.9 13 / 17
17.1.8 13 / 17
17.1.7 13 / 17
17.1.6 13 / 17

v17.2.20

1 finding
INFO No provenance attestation provenance

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

v17.2.19

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.

v17.2.18

1 finding
INFO No provenance attestation provenance

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

v17.2.17

1 finding
INFO No provenance attestation provenance

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

v17.2.16

1 finding
INFO No provenance attestation provenance

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

v17.2.15

1 finding
INFO No provenance attestation provenance

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

v17.2.14

1 finding
INFO No provenance attestation provenance

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

v17.2.13

1 finding
INFO No provenance attestation provenance

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

v17.2.12

1 finding
INFO No provenance attestation provenance

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

v17.2.11

1 finding
INFO No provenance attestation provenance

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

v17.2.10

1 finding
INFO No provenance attestation provenance

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

v17.2.9

1 finding
INFO No provenance attestation provenance

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

v17.2.8

1 finding
INFO No provenance attestation provenance

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

v17.2.7

1 finding
INFO No provenance attestation provenance

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

v17.2.6

1 finding
INFO No provenance attestation provenance

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

v17.2.5

1 finding
INFO No provenance attestation provenance

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

v17.2.4

1 finding
INFO No provenance attestation provenance

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

v17.2.3

1 finding
INFO No provenance attestation provenance

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

v17.2.2

1 finding
INFO No provenance attestation provenance

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

v17.2.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.

v17.2.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.

v17.1.27

1 finding
INFO No provenance attestation provenance

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

v17.1.26

1 finding
INFO No provenance attestation provenance

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

v17.1.25

1 finding
INFO No provenance attestation provenance

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

v17.1.24

1 finding
INFO No provenance attestation provenance

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

v17.1.23

1 finding
INFO No provenance attestation provenance

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

v17.1.22

1 finding
INFO No provenance attestation provenance

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

v17.1.21

1 finding
INFO No provenance attestation provenance

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

v17.1.20

1 finding
INFO No provenance attestation provenance

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

v17.1.19

1 finding
INFO No provenance attestation provenance

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

v17.1.18

1 finding
INFO No provenance attestation provenance

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

v17.1.17

1 finding
INFO No provenance attestation provenance

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

v17.1.16

1 finding
INFO No provenance attestation provenance

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

v17.1.15

1 finding
INFO No provenance attestation provenance

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

v17.1.14

1 finding
INFO No provenance attestation provenance

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

v17.1.13

1 finding
INFO No provenance attestation provenance

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

v17.1.12

1 finding
INFO No provenance attestation provenance

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

v17.1.11

1 finding
INFO No provenance attestation provenance

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

v17.1.10

1 finding
INFO No provenance attestation provenance

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

v17.1.9

1 finding
INFO No provenance attestation provenance

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

v17.1.8

1 finding
INFO No provenance attestation provenance

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

v17.1.7

1 finding
INFO No provenance attestation provenance

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

v17.1.6

1 finding
INFO No provenance attestation provenance

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