← Home

@atlaskit/native-embeds-common

npm Repository Homepage

A shared package for native embeds to be used across experiences and plugin

19
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Atlassian monorepo packages routinely publish at 0.0.0 as an initial/internal release convention. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): Runtime polyfill injected by Babel toolchain; not directly imported by convention. ai
phantom-deps phantom-dep:@compiled/react AI (phantom-deps): CSS-in-JS framework dependency referenced via config/build tooling, not direct imports. ai
dependencies unvetted-dep:react-intl-next AI (dependencies): react-intl-next is Atlassian's standard npm alias for react-intl; stable pattern across the atlaskit monorepo. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): @atlaskit/tokens is a design-token peer used at build/CSS level; not directly imported in JS but legitimately declared. ai

Versions (showing 19 of 19)

Version Deps Published
1.5.0 10 / 7
1.4.1 10 / 7
1.4.0 10 / 7
1.3.1 10 / 6
1.3.0 10 / 6
1.2.0 10 / 6
1.1.1 10 / 6
1.1.0 10 / 6
1.0.2 10 / 6
1.0.1 10 / 6
1.0.0 10 / 6
0.2.3 11 / 5
0.2.2 11 / 5
0.2.1 5 / 5
0.2.0 5 / 5
0.1.2 5 / 5
0.1.1 4 / 5
0.1.0 3 / 5
0.0.0 2 / 5

v1.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.