@atlaskit/linking-types
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 publishes the entire @atlaskit namespace without Sigstore provenance; this is a stable organizational pattern, not a risk signal for this package. | ai | |
| dependencies | unvetted-dep:@atlaskit/json-ld-types | AI (dependencies): @atlaskit/json-ld-types is a first-party Atlassian package in the same @atlaskit namespace; unvetted status reflects review queue lag, not a real risk. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 14.4.0 | 2 / 3 | |
| 14.3.0 | 2 / 3 | |
| 14.2.1 | 2 / 2 | |
| 14.2.0 | 2 / 2 | |
| 14.1.0 | 2 / 2 | |
| 14.0.1 | 2 / 2 | |
| 14.0.0 | 2 / 3 |
v14.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.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.
v14.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.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.