@atlaskit/embedded-confluence
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:@babel/runtime | AI (phantom-deps): @babel/runtime is a build-time helper injected by Babel transpilation; phantom detection is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-intl-next | AI (phantom-deps): react-intl-next is an npm alias for react-intl used in Atlassian's ecosystem; referenced in config files rather than direct imports is expected. | ai | |
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): npm alias pattern (npm:react-intl@^5.18.1) is a standard Atlassian ecosystem practice; resolves to the well-known react-intl package, not a security risk. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.1.0 | 1 / 7 | |
| 5.0.1 | 1 / 7 | |
| 5.0.0 | 1 / 6 | |
| 4.5.2 | 2 / 5 | |
| 4.5.0 | 2 / 5 |
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.