← Home

@atlaskit/ufo

npm Repository Homepage
4
Versions
—
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
provenance no-provenance AI (provenance): Atlassian's atlaskit packages consistently publish without Sigstore provenance; this is a stable pattern for this publisher and not a security concern. ai
phantom-deps phantom-dep:@atlaskit/platform-feature-flags AI (phantom-deps): Same-org Atlaskit dependency declared but not directly imported; consistent with Atlassian's monorepo patterns. No malicious signal. ai

Versions (showing 4 of 4)

Version Deps Published
0.5.0 3 / 0
0.4.3 3 / 0
0.4.2 3 / 0
0.4.1 2 / 0

v0.5.0

1 finding
INFO No provenance attestation provenance

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

v0.4.3

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.4.2

1 finding
INFO No provenance attestation provenance

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