@atlaskit/util-service-support No license 31 versions

@atlaskit/util-service-support

npm Repository Homepage

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

Maintainers

atlassianartifactteam

Keywords

fabricuiprivate

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@atlassian/react-compiler-gating	AI (phantom-deps): Same Atlassian org scope; declared in config only, not imported at runtime. Stable false positive for this package.	ai	2026/07/02
phantom-deps	phantom-dep:@atlaskit/platform-feature-flags	AI (phantom-deps): Same-org @atlaskit scoped dependency declared but not directly imported; consistent with monorepo packaging patterns, not a security concern.	ai	2026/04/24

Versions (showing 31 of 31)

Version	Deps	Published
7.2.0	5 / 3	2026-07-08
7.1.0	5 / 3	2026-06-26
7.0.1	5 / 3	2026-06-23
7.0.0	4 / 4	2026-06-16
6.4.2	4 / 4	2026-05-21
6.4.1	4 / 4	2026-05-20
6.4.0	4 / 3	2026-05-14
6.3.5	4 / 3	2026-02-12
6.3.4	4 / 3	2026-01-20
6.3.3	4 / 3	2025-08-25
6.3.2	4 / 4	2025-07-16
6.3.1	4 / 4	2025-03-20
6.3.0	4 / 4	2025-03-11
6.2.7	3 / 4	2025-02-24
6.2.6	3 / 4	2025-02-04
6.2.5	1 / 5	2024-03-20
6.2.4	1 / 5	2024-01-29
6.2.3	1 / 5	2023-08-21
6.2.2	1 / 6	2023-05-17
6.2.1	1 / 6	2023-05-15
6.2.0	1 / 6	2023-05-08
6.1.3	1 / 6	2022-10-04
6.1.2	1 / 6	2022-08-25
6.1.1	1 / 6	2022-04-26
6.1.0	1 / 6	2022-01-28
6.0.5	3 / 5	2021-03-30
6.0.4	3 / 5	2021-03-30
6.0.3	3 / 5	2020-11-19
6.0.2	3 / 5	2020-10-15
6.0.1	3 / 4	2020-08-24
6.0.0	3 / 4	2020-07-02

v7.2.0

1 finding

LOW No provenance attestation provenance

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

v6.3.1

1 finding

LOW No provenance attestation provenance

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

v6.3.0

1 finding

LOW No provenance attestation provenance

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

v6.2.7

1 finding

LOW No provenance attestation provenance

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

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

v6.2.5

1 finding

LOW No provenance attestation provenance

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

v6.2.4

1 finding

LOW No provenance attestation provenance

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

v6.2.3

1 finding

LOW No provenance attestation provenance

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

v6.2.2

1 finding

LOW No provenance attestation provenance

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

v6.2.1

1 finding

LOW No provenance attestation provenance

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

v6.2.0

1 finding

LOW No provenance attestation provenance

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

v6.1.3

1 finding

LOW No provenance attestation provenance

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

v6.1.2

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v6.0.4

1 finding

LOW No provenance attestation provenance

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

v6.0.3

1 finding

LOW No provenance attestation provenance

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

v6.0.2

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. Consider requesting the maintainer enable provenance via CI/CD.

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