← Home

@atlaskit/link-picker

51
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@atlassian/react-compiler-gating AI (phantom-deps): Same Atlassian org scope; declared for config use only, not directly imported at runtime. ai
phantom-deps phantom-dep:@atlaskit/css AI (phantom-deps): Declared dependency in monorepo component library; typical for Atlassian packages managing shared styles. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): Declared dependency in monorepo component library; typical for Atlassian design token usage. ai
phantom-deps phantom-dep:@react-loosely-lazy/manifest AI (phantom-deps): Declared dependency referenced in config; legitimate for code-splitting in component library. ai
phantom-deps phantom-dep:@atlaskit/afm-i18n-platform-linking-platform-link-picker AI (phantom-deps): Declared i18n dependency; typical for Atlassian packages with internationalization support. ai
bogus-package bogus-package AI (bogus-package): Atlaskit component packages routinely have minimal READMEs and no keywords; this is a structural pattern of the Atlassian Design System monorepo, not a spam indicator. ai
provenance no-provenance AI (provenance): Atlassian publishes @atlaskit packages without Sigstore provenance; this is consistent across the entire package family and not a security risk given the verified publisher track record. ai

Versions (showing 51 of 67)

View all versions
Version Deps Published
6.3.0 33 / 24
6.2.7 33 / 24
6.2.6 33 / 23
6.2.5 33 / 23
6.2.4 33 / 23
6.2.3 33 / 23
6.2.2 33 / 23
6.2.1 33 / 23
6.2.0 33 / 23
6.1.0 33 / 23
6.0.2 33 / 23
6.0.1 33 / 23
6.0.0 32 / 24
5.3.4 32 / 24
5.3.3 32 / 24
5.3.2 32 / 24
5.3.1 32 / 24
5.3.0 32 / 24
5.2.1 32 / 24
5.2.0 32 / 23
5.1.7 32 / 23
5.1.6 32 / 23
5.1.5 32 / 23
5.1.4 32 / 23
5.1.3 32 / 23
5.1.2 32 / 23
5.1.1 33 / 22
5.1.0 33 / 21
5.0.1 33 / 21
5.0.0 33 / 21
4.2.24 32 / 20
4.2.23 32 / 20
4.2.22 32 / 20
4.2.21 32 / 19
4.2.20 32 / 19
4.2.19 32 / 19
4.2.18 32 / 19
4.2.17 33 / 19
4.2.16 33 / 19
4.2.15 33 / 19
4.2.14 33 / 19
4.2.13 33 / 19
4.2.12 33 / 19
4.2.11 33 / 19
4.2.10 33 / 19
4.2.9 33 / 19
4.2.8 33 / 19
4.2.7 33 / 19
4.2.6 33 / 19
4.2.5 33 / 19
4.2.4 33 / 19

v6.3.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.

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

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

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

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

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

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

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