@atlaskit/teams-app-internal-navigation
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@atlaskit/link | AI (dependencies): @atlaskit/link is an Atlassian-owned design system package; expected dependency for Atlaskit navigation components. | ai | |
| dependencies | unvetted-dep:@atlaskit/menu | AI (dependencies): @atlaskit/menu is an Atlassian-owned design system package; expected dependency for Atlaskit navigation components. | ai | |
| dependencies | unvetted-dep:@atlaskit/button | AI (dependencies): @atlaskit/button is an Atlassian-owned design system package; expected dependency for Atlaskit navigation components. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): @atlaskit/primitives is an Atlassian-owned design system package; expected dependency for Atlaskit navigation components. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes many packages without Sigstore provenance; consistent with their established publishing pipeline. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.9.0 | 6 / 8 | |
| 1.8.6 | 5 / 8 | |
| 1.8.5 | 5 / 8 | |
| 1.8.4 | 5 / 7 | |
| 1.8.3 | 5 / 7 | |
| 1.8.2 | 5 / 6 | |
| 1.8.1 | 5 / 6 | |
| 1.8.0 | 5 / 6 | |
| 1.7.0 | 5 / 6 | |
| 1.6.2 | 5 / 6 | |
| 1.6.1 | 5 / 6 | |
| 1.6.0 | 5 / 6 | |
| 1.5.1 | 5 / 6 | |
| 1.5.0 | 5 / 6 | |
| 1.4.0 | 5 / 6 | |
| 1.3.0 | 5 / 6 | |
| 1.2.1 | 2 / 6 | |
| 1.2.0 | 2 / 6 | |
| 1.1.0 | 2 / 5 | |
| 1.0.1 | 2 / 5 | |
| 1.0.0 | 2 / 5 |
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.