← Home

@atlaskit/form

31
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

Keywords

atlaskitreactui

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): @atlaskit/form is a scoped Atlassian package with 2900+ days of history; levenshtein match to 'cors' is a clear false positive with no plausible impersonation intent. ai
dependencies unvetted-dep:@atlaskit/css AI (dependencies): Internal @atlaskit scoped dependency from the same Atlassian org; expected for this component package. ai
dependencies unvetted-dep:@atlaskit/icon AI (dependencies): Internal @atlaskit scoped dependency from the same Atlassian org; expected for this component package. ai
dependencies unvetted-dep:@atlaskit/tokens AI (dependencies): Internal @atlaskit scoped dependency from the same Atlassian org; expected design token dependency. ai
dependencies unvetted-dep:@atlaskit/heading AI (dependencies): Internal @atlaskit scoped dependency from the same Atlassian org; expected for this component package. ai
dependencies unvetted-dep:@atlaskit/primitives AI (dependencies): Internal @atlaskit scoped dependency from the same Atlassian org; expected for this component package. ai
dependencies unvetted-dep:@atlaskit/platform-feature-flags AI (dependencies): Internal @atlaskit scoped dependency from the same Atlassian org; expected for feature flag gating. ai
dependencies unvetted-dep:final-form-focus AI (dependencies): final-form-focus is a well-known companion package to final-form; expected dependency for a form component. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): Design token packages are commonly declared as deps for transitive/runtime use without direct imports; same org scope, no risk. ai
phantom-deps phantom-dep:@atlaskit/platform-feature-flags AI (phantom-deps): Feature flag packages may be used indirectly; same org scope, no risk. ai

Versions (showing 31 of 31)

Version Deps Published
15.5.6 13 / 31
15.5.5 13 / 31
15.5.4 13 / 31
15.5.3 13 / 31
15.5.2 13 / 30
15.5.1 13 / 30
15.5.0 13 / 30
15.4.2 13 / 30
15.4.1 13 / 29
15.4.0 13 / 29
15.3.7 13 / 29
15.3.6 13 / 29
15.3.5 13 / 29
15.3.4 13 / 29
15.3.3 13 / 29
15.3.2 13 / 29
15.3.1 13 / 29
15.3.0 13 / 30
15.2.0 13 / 30
15.1.2 13 / 29
15.1.1 13 / 29
15.1.0 13 / 29
15.0.1 13 / 29
15.0.0 13 / 28
14.4.0 13 / 28
14.3.2 11 / 28
14.3.1 11 / 28
14.3.0 11 / 28
14.2.7 11 / 28
14.2.6 11 / 28
14.2.5 11 / 28

v15.5.6

1 finding
LOW No provenance attestation provenance

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

v15.5.5

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

1 finding
LOW No provenance attestation provenance

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

v15.5.3

1 finding
LOW No provenance attestation provenance

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

v15.5.2

1 finding
LOW No provenance attestation provenance

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

v15.5.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.

v15.5.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.

v15.4.2

1 finding
LOW No provenance attestation provenance

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

v15.4.1

1 finding
LOW No provenance attestation provenance

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

v15.4.0

1 finding
LOW No provenance attestation provenance

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

v15.3.7

1 finding
LOW No provenance attestation provenance

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

v15.3.6

1 finding
LOW No provenance attestation provenance

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

v15.3.5

1 finding
LOW No provenance attestation provenance

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

v15.3.4

1 finding
LOW No provenance attestation provenance

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

v15.3.3

1 finding
LOW No provenance attestation provenance

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

v15.3.2

1 finding
LOW No provenance attestation provenance

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

v15.3.1

1 finding
LOW No provenance attestation provenance

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

v15.3.0

1 finding
LOW No provenance attestation provenance

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

v15.2.0

1 finding
LOW No provenance attestation provenance

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

v15.1.2

1 finding
LOW No provenance attestation provenance

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

v15.1.1

1 finding
LOW No provenance attestation provenance

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

v15.1.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.1

1 finding
LOW No provenance attestation provenance

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

v15.0.0

1 finding
LOW No provenance attestation provenance

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

v14.4.0

1 finding
LOW No provenance attestation provenance

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

v14.3.2

1 finding
LOW No provenance attestation provenance

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

v14.3.1

1 finding
LOW No provenance attestation provenance

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

v14.3.0

1 finding
LOW No provenance attestation provenance

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

v14.2.7

1 finding
LOW No provenance attestation provenance

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

v14.2.6

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.

v14.2.5

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.