← Home

@atlaskit/editor-plugin-autocomplete

npm Repository Homepage
15
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:wink-nlp AI (dependencies): wink-nlp is a legitimate NLP library; its use in an autocomplete editor plugin is expected and consistent with the package's purpose. ai
dependencies unvetted-dep:@atlaskit/editor-prosemirror AI (dependencies): @atlaskit/editor-prosemirror is an Atlassian-owned ProseMirror wrapper; expected dependency for Atlaskit editor plugins. ai
phantom-deps phantom-dep:wink-nlp AI (phantom-deps): Declared in config files but not directly imported; consistent with optional/build-time usage in an NLP-based autocomplete plugin. ai
phantom-deps phantom-dep:compromise AI (phantom-deps): Declared in config files but not directly imported; consistent with optional NLP dependency usage in this autocomplete plugin. ai

Versions (showing 15 of 15)

Version Deps Published
3.1.0 6 / 1
3.0.0 6 / 1
2.5.2 6 / 1
2.5.1 6 / 1
2.5.0 6 / 1
2.4.0 4 / 0
2.3.0 4 / 0
2.2.0 4 / 0
2.1.0 4 / 0
2.0.0 4 / 0
1.0.0 4 / 0
0.4.0 4 / 0
0.3.0 4 / 0
0.2.0 4 / 0
0.1.0 4 / 0

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.5.2

1 finding
LOW No provenance attestation provenance

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

v2.5.1

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

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