@atlaskit/teams-app-internal-analytics No license 52 versions

@atlaskit/teams-app-internal-analytics

npm Repository Homepage

52

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.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@atlaskit/css	AI (phantom-deps): Phantom dependency in monorepo context; same-org scope, legitimate transitive use pattern.	ai	2026/04/26
phantom-deps	phantom-dep:@atlaskit/tokens	AI (phantom-deps): Phantom dependency in monorepo context; same-org scope, legitimate transitive use pattern.	ai	2026/04/26
phantom-deps	phantom-dep:@atlaskit/primitives	AI (phantom-deps): Phantom dependency in monorepo context; same-org scope, legitimate transitive use pattern.	ai	2026/04/26
phantom-deps	phantom-dep:@compiled/react	AI (phantom-deps): Legitimate CSS-in-JS library used by Atlaskit; referenced in config files as documented in package.json sideEffects/techstack.	ai	2026/04/25
dependencies	unvetted-dep:@atlaskit/analytics-next	AI (dependencies): First-party Atlaskit package from the same Atlassian Frontend monorepo; no security risk.	ai	2026/04/25
phantom-deps	phantom-dep:@atlaskit/analytics-listeners	AI (phantom-deps): Same-org first-party dependency; phantom usage consistent with monorepo type declarations or transitive usage patterns.	ai	2026/04/25
dependencies	unvetted-dep:@atlaskit/analytics-listeners	AI (dependencies): First-party Atlaskit package from the same Atlassian Frontend monorepo; no security risk.	ai	2026/04/25
dependencies	unvetted-dep:@atlaskit/analytics-namespaced-context	AI (dependencies): First-party Atlaskit package from the same Atlassian Frontend monorepo; no security risk.	ai	2026/04/25

Versions (showing 52 of 52)

Version	Deps	Published
1.32.0	5 / 11	2026-05-27
1.31.0	5 / 10	2026-05-21
1.30.0	5 / 10	2026-05-18
1.29.0	5 / 10	2026-05-13
1.28.0	5 / 10	2026-05-11
1.27.5	5 / 10	2026-04-23
1.27.4	5 / 8	2026-04-20
1.27.3	5 / 7	2026-03-16
1.27.2	5 / 7	2026-03-09
1.27.1	5 / 7	2026-03-09
1.27.0	5 / 7	2026-03-04
1.26.0	5 / 7	2026-02-27
1.25.3	5 / 7	2026-02-25
1.25.2	5 / 7	2026-02-24
1.25.1	5 / 7	2026-02-23
1.25.0	5 / 7	2026-02-23
1.24.2	5 / 7	2026-02-19
1.24.1	5 / 7	2026-02-09
1.24.0	5 / 7	2026-02-02
1.23.2	5 / 7	2026-01-21
1.23.1	5 / 8	2025-12-24
1.23.0	5 / 8	2025-12-18
1.22.0	5 / 8	2025-12-11
1.21.0	5 / 8	2025-12-10
1.20.3	5 / 8	2025-12-09
1.20.2	8 / 8	2025-11-24
1.20.1	8 / 8	2025-11-20
1.20.0	8 / 8	2025-11-19
1.19.2	8 / 8	2025-11-07
1.19.1	8 / 8	2025-11-03
1.19.0	8 / 8	2025-10-29
1.18.0	8 / 8	2025-10-21
1.17.2	8 / 8	2025-10-16
1.17.1	8 / 8	2025-10-15
1.17.0	8 / 8	2025-10-15
1.16.0	8 / 8	2025-10-13
1.15.0	8 / 8	2025-10-10
1.14.0	8 / 8	2025-10-07
1.13.0	8 / 8	2025-10-03
1.12.0	8 / 8	2025-10-03
1.11.0	8 / 8	2025-10-02
1.10.0	8 / 8	2025-10-02
1.9.0	8 / 8	2025-10-02
1.8.0	8 / 8	2025-10-01
1.7.0	8 / 8	2025-09-26
1.6.0	8 / 8	2025-09-23
1.5.0	8 / 8	2025-09-22
1.4.0	8 / 8	2025-09-17
1.3.0	8 / 8	2025-09-16
1.2.0	8 / 8	2025-09-12
1.1.0	8 / 7	2025-09-11
1.0.0	8 / 7	2025-09-08

v1.32.0

1 finding

LOW No provenance attestation provenance

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

v1.31.0

1 finding

LOW No provenance attestation provenance

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

v1.30.0

1 finding

LOW No provenance attestation provenance

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

v1.29.0

1 finding

LOW No provenance attestation provenance

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

v1.28.0

1 finding

LOW No provenance attestation provenance

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

v1.27.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.

v1.27.4

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.

v1.27.3

1 finding

LOW No provenance attestation provenance

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

v1.27.2

1 finding

LOW No provenance attestation provenance

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

v1.27.1

1 finding

LOW No provenance attestation provenance

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

v1.27.0

1 finding

LOW No provenance attestation provenance

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

v1.26.0

1 finding

LOW No provenance attestation provenance

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

v1.25.3

1 finding

LOW No provenance attestation provenance

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

v1.25.2

1 finding

LOW No provenance attestation provenance

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

v1.25.1

1 finding

LOW No provenance attestation provenance

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

v1.25.0

1 finding

LOW No provenance attestation provenance

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

v1.24.2

1 finding

LOW No provenance attestation provenance

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

v1.24.1

1 finding

LOW No provenance attestation provenance

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

v1.24.0

1 finding

LOW No provenance attestation provenance

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

v1.23.2

1 finding

LOW No provenance attestation provenance

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

v1.23.1

1 finding

LOW No provenance attestation provenance

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

v1.23.0

1 finding

LOW No provenance attestation provenance

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

v1.22.0

1 finding

LOW No provenance attestation provenance

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

v1.21.0

1 finding

LOW No provenance attestation provenance

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

v1.20.3

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.

v1.20.2

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.

v1.20.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.

v1.20.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.

v1.19.2

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.

v1.19.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.

v1.19.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.

v1.17.0

1 finding

LOW No provenance attestation provenance

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