@atlaskit/link-extractors
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Atlassian's atlaskit packages are published by a trusted, established publisher account; lack of Sigstore provenance is not a meaningful risk signal for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.7.0 | 5 / 7 | |
| 2.6.0 | 5 / 6 | |
| 2.5.0 | 5 / 6 | |
| 2.4.8 | 5 / 5 | |
| 2.4.7 | 5 / 5 | |
| 2.4.6 | 5 / 4 | |
| 2.4.5 | 5 / 4 | |
| 2.4.4 | 5 / 4 | |
| 2.4.3 | 5 / 4 | |
| 2.4.2 | 5 / 5 | |
| 2.4.1 | 5 / 5 | |
| 2.4.0 | 5 / 5 | |
| 2.3.9 | 5 / 5 | |
| 2.3.8 | 4 / 4 | |
| 2.3.7 | 4 / 4 | |
| 2.3.6 | 4 / 4 | |
| 2.3.5 | 4 / 4 | |
| 2.3.4 | 4 / 4 | |
| 2.3.3 | 4 / 4 | |
| 2.3.2 | 4 / 4 | |
| 2.3.1 | 4 / 4 | |
| 2.3.0 | 4 / 4 |
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.