@atlaskit/icon-object
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): First-party Atlassian Design System dependency within the same @atlaskit scope; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@atlaskit/object | AI (dependencies): First-party Atlassian Design System dependency within the same @atlaskit scope; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party Atlassian Design System dependency within the same @atlaskit scope; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org @atlaskit scope; declared but used transitively or in compiled CSS output. No risk for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 7.5.7 | 5 / 12 | |
| 7.5.6 | 5 / 12 | |
| 7.5.5 | 5 / 12 | |
| 7.5.4 | 5 / 12 | |
| 7.5.3 | 5 / 11 | |
| 7.5.2 | 5 / 11 | |
| 7.5.1 | 5 / 11 | |
| 7.5.0 | 5 / 11 | |
| 7.4.3 | 7 / 11 | |
| 7.4.2 | 7 / 11 | |
| 7.4.1 | 5 / 11 | |
| 7.4.0 | 5 / 11 | |
| 7.3.4 | 5 / 11 | |
| 7.3.3 | 5 / 11 | |
| 7.3.2 | 5 / 11 | |
| 7.3.1 | 5 / 11 | |
| 7.3.0 | 5 / 11 | |
| 7.2.3 | 5 / 11 | |
| 7.2.2 | 3 / 10 | |
| 7.2.1 | 3 / 11 | |
| 7.2.0 | 3 / 11 | |
| 7.1.4 | 4 / 11 | |
| 7.1.3 | 4 / 11 | |
| 7.1.2 | 4 / 11 | |
| 7.1.1 | 4 / 11 |
v7.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.