@atlaskit/link-client-extension No license 4 versions

@atlaskit/link-client-extension

npm Repository Homepage

Versions

—

License

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.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:lru_map	AI (dependencies): lru_map is a well-known, stable LRU cache utility with no known security issues; stable false positive for this package.	ai	2026/04/24
dependencies	unvetted-dep:@atlaskit/json-ld-types	AI (dependencies): Internal Atlassian package from the same atlassian-frontend-mirror monorepo; no security concern.	ai	2026/04/24
dependencies	unvetted-dep:@atlaskit/linking-types	AI (dependencies): Internal Atlassian package from the same atlassian-frontend-mirror monorepo; no security concern.	ai	2026/04/24
dependencies	unvetted-dep:@atlaskit/linking-common	AI (dependencies): Internal Atlassian package from the same atlassian-frontend-mirror monorepo; no security concern.	ai	2026/04/24
dependencies	unvetted-dep:@atlaskit/platform-feature-flags	AI (dependencies): Internal Atlassian package from the same atlassian-frontend-mirror monorepo; no security concern.	ai	2026/04/24
phantom-deps	phantom-dep:@atlaskit/platform-feature-flags	AI (phantom-deps): Same-org Atlassian package declared but not directly imported; consistent with monorepo transitive usage patterns.	ai	2026/04/24

Versions (showing 4 of 4)

Version	Deps	Published
6.1.1	6 / 8	2026-05-29
6.1.0	6 / 7	2026-05-21
6.0.1	6 / 6	2026-04-09
6.0.0	6 / 6	2025-09-11

v6.1.1

1 finding

LOW No provenance attestation provenance

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

v6.1.0

1 finding

LOW No provenance attestation provenance

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

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