@atlaskit/lozenge
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlaskit/css | AI (phantom-deps): Phantom deps in @atlaskit scope are typical for design system monorepos; shared infrastructure dependencies. | ai | |
| phantom-deps | phantom-dep:@atlaskit/theme | AI (phantom-deps): Phantom deps in @atlaskit scope are typical for design system monorepos; shared infrastructure dependencies. | ai | |
| phantom-deps | phantom-dep:@atlaskit/primitives | AI (phantom-deps): Phantom deps in @atlaskit scope are typical for design system monorepos; shared infrastructure dependencies. | ai | |
| phantom-deps | phantom-dep:@atlaskit/codemod-utils | AI (phantom-deps): Phantom deps in @atlaskit scope are typical for design system monorepos; shared infrastructure dependencies. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party @atlaskit sibling dependency; intra-org dependency is expected and benign for this monorepo package. | ai | |
| dependencies | unvetted-dep:@atlaskit/spinner | AI (dependencies): First-party @atlaskit sibling dependency; intra-org dependency is expected and benign for this monorepo package. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): First-party @atlaskit sibling dependency; intra-org dependency is expected and benign for this monorepo package. | ai | |
| dependencies | unvetted-dep:@atlaskit/css | AI (dependencies): First-party @atlaskit sibling dependency; intra-org dependency is expected and benign for this monorepo package. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party @atlaskit sibling dependency; intra-org dependency is expected and benign for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Phantom dep within same org scope; transitive usage in monorepo setups is normal and not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/analytics-next | AI (dependencies): First-party @atlaskit sibling dependency; intra-org dependency is expected and benign for this monorepo package. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): First-party @atlaskit sibling dependency; intra-org dependency is expected and benign for this monorepo package. | ai | |
| dependencies | unvetted-dep:@atlaskit/badge | AI (dependencies): First-party @atlaskit sibling dependency; intra-org dependency is expected and benign for this monorepo package. | ai | |
| dependencies | unvetted-dep:@atlaskit/motion | AI (dependencies): First-party @atlaskit sibling dependency; intra-org dependency is expected and benign for this monorepo package. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 13.8.3 | 12 / 16 | |
| 13.8.2 | 12 / 15 | |
| 13.8.1 | 12 / 15 | |
| 13.8.0 | 12 / 15 | |
| 13.7.1 | 12 / 15 | |
| 13.7.0 | 12 / 15 | |
| 13.6.1 | 12 / 15 | |
| 13.6.0 | 12 / 15 | |
| 13.5.7 | 11 / 15 | |
| 13.5.6 | 11 / 15 | |
| 13.5.5 | 11 / 14 | |
| 13.5.4 | 11 / 14 | |
| 13.5.3 | 11 / 14 | |
| 13.5.2 | 11 / 14 | |
| 13.5.1 | 11 / 13 | |
| 13.5.0 | 11 / 13 | |
| 13.4.5 | 11 / 13 | |
| 13.4.4 | 11 / 13 | |
| 13.4.3 | 11 / 13 | |
| 13.4.2 | 11 / 13 | |
| 13.4.1 | 9 / 13 | |
| 13.4.0 | 9 / 13 | |
| 13.3.4 | 9 / 13 | |
| 13.3.3 | 9 / 13 | |
| 13.3.2 | 9 / 13 | |
| 13.3.1 | 9 / 13 | |
| 13.3.0 | 9 / 13 | |
| 13.2.2 | 9 / 13 | |
| 13.2.1 | 9 / 13 | |
| 13.2.0 | 9 / 13 | |
| 13.1.2 | 8 / 14 | |
| 13.1.1 | 8 / 14 | |
| 13.1.0 | 8 / 14 | |
| 13.0.15 | 8 / 14 | |
| 13.0.14 | 8 / 14 | |
| 13.0.13 | 8 / 14 | |
| 13.0.12 | 8 / 14 | |
| 13.0.11 | 8 / 14 | |
| 13.0.10 | 8 / 14 | |
| 13.0.9 | 8 / 14 | |
| 13.0.8 | 8 / 14 | |
| 13.0.7 | 8 / 14 | |
| 13.0.6 | 8 / 14 | |
| 13.0.5 | 8 / 15 | |
| 13.0.4 | 8 / 15 | |
| 13.0.3 | 8 / 15 | |
| 13.0.2 | 8 / 15 | |
| 13.0.1 | 8 / 15 | |
| 13.0.0 | 8 / 15 |
v13.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.