@atlaskit/css
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 | publisher-changed | AI (provenance): Legitimate Atlassian publisher migration; atlassianartifactteam has 8600+ approved packages. | ai | |
| provenance | missing-githead | AI (provenance): Publish environment changed with Atlassian's account migration; expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): atlaskit account replaced by equivalent Atlassian org accounts; expected rotation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atlassianartifactteam and atlaskit-user are Atlassian org accounts; stable for this package. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Atlassian internal account rotation; atlaskit-user confirmed as known maintainer on prior versions. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @atlaskit/css is a legitimate scoped Atlassian design system package, not a typosquat of 'cors'. The @atlaskit namespace is well-established. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @atlaskit/css is a legitimate scoped Atlassian design system package, not a typosquat of 'qs'. The @atlaskit namespace is well-established. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 3 / 11 | |
| 0.19.4 | 3 / 10 | |
| 0.19.3 | 3 / 10 | |
| 0.19.2 | 3 / 9 | |
| 0.19.1 | 3 / 9 | |
| 0.19.0 | 3 / 9 | |
| 0.18.1 | 3 / 9 | |
| 0.18.0 | 3 / 9 | |
| 0.17.1 | 3 / 9 | |
| 0.17.0 | 3 / 9 | |
| 0.16.0 | 3 / 9 | |
| 0.15.2 | 3 / 9 | |
| 0.15.1 | 3 / 9 | |
| 0.15.0 | 3 / 9 | |
| 0.14.4 | 3 / 9 | |
| 0.14.3 | 3 / 9 | |
| 0.14.2 | 3 / 9 | |
| 0.14.1 | 3 / 9 | |
| 0.14.0 | 3 / 9 | |
| 0.13.1 | 3 / 9 | |
| 0.13.0 | 3 / 9 | |
| 0.12.5 | 3 / 9 | |
| 0.12.4 | 3 / 9 | |
| 0.12.3 | 3 / 9 | |
| 0.12.2 | 3 / 10 | |
| 0.12.1 | 3 / 10 | |
| 0.12.0 | 3 / 10 | |
| 0.11.0 | 3 / 10 | |
| 0.10.7 | 3 / 10 | |
| 0.10.6 | 3 / 10 | |
| 0.10.5 | 3 / 10 | |
| 0.10.4 | 3 / 10 | |
| 0.10.3 | 3 / 10 | |
| 0.10.2 | 3 / 10 | |
| 0.10.1 | 3 / 10 | |
| 0.10.0 | 3 / 10 | |
| 0.9.0 | 3 / 10 | |
| 0.8.0 | 3 / 10 | |
| 0.7.5 | 3 / 10 | |
| 0.7.4 | 4 / 11 | |
| 0.7.2 | 4 / 12 | |
| 0.6.2 | 3 / 12 | |
| 0.6.1 | 3 / 12 | |
| 0.6.0 | 3 / 12 | |
| 0.5.3 | 3 / 12 | |
| 0.5.2 | 3 / 12 | |
| 0.5.1 | 3 / 8 | |
| 0.5.0 | 3 / 8 | |
| 0.4.0 | 3 / 8 | |
| 0.3.0 | 3 / 8 | |
| 0.2.0 | 3 / 8 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-03-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-03-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-03-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-03-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-02-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-01-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-01-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-01-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2024-12-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
3 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atlaskit-user) than the most recent previously approved version (atlaskit) on 2024-11-21, but atlaskit-user is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.6.1
3 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atlaskit-user) than the most recent previously approved version (atlaskit) on 2024-11-07, but atlaskit-user is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.6.0
3 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atlaskit-user) than the most recent previously approved version (atlaskit) on 2024-10-23, but atlaskit-user is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.