← Home

@atlaskit/object

npm Repository Homepage

An object is an icon that represents an Atlassian-specific content type.

18
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
dependencies unvetted-dep:@atlaskit/css AI (dependencies): First-party @atlaskit org dependency from the same publisher; legitimate internal design system package. ai
dependencies unvetted-dep:@atlaskit/icon AI (dependencies): First-party @atlaskit org dependency from the same publisher; legitimate internal design system package. ai
dependencies unvetted-dep:@atlaskit/tile AI (dependencies): First-party @atlaskit org dependency from the same publisher; legitimate internal design system package. ai
dependencies unvetted-dep:@atlaskit/tokens AI (dependencies): First-party @atlaskit org dependency from the same publisher; legitimate internal design system package. ai
dependencies unvetted-dep:@atlaskit/icon-lab AI (dependencies): First-party @atlaskit org dependency from the same publisher; legitimate internal design system package. ai
dependencies unvetted-dep:@atlaskit/primitives AI (dependencies): First-party @atlaskit org dependency from the same publisher; legitimate internal design system package. ai
phantom-deps phantom-dep:@atlaskit/css AI (phantom-deps): Phantom dep pattern is consistent with Atlaskit monorepo CSS-in-JS build tooling; not a security concern. ai
phantom-deps phantom-dep:@compiled/react AI (phantom-deps): Compiled/react is Atlassian's CSS-in-JS build tool; declared in config files as expected for this monorepo pattern. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): Phantom dep pattern is consistent with Atlaskit monorepo design token build tooling; not a security concern. ai
phantom-deps phantom-dep:@atlaskit/primitives AI (phantom-deps): Phantom dep pattern is consistent with Atlaskit monorepo build tooling; not a security concern. ai

Versions (showing 18 of 18)

Version Deps Published
1.0.17 9 / 14
1.0.16 9 / 14
1.0.15 9 / 14
1.0.14 9 / 14
1.0.13 9 / 13
1.0.12 9 / 13
1.0.11 9 / 12
1.0.10 9 / 12
1.0.9 9 / 12
1.0.8 9 / 12
1.0.7 9 / 12
1.0.6 9 / 12
1.0.5 9 / 12
1.0.4 9 / 13
1.0.3 9 / 13
1.0.2 9 / 13
1.0.1 9 / 13
1.0.0 9 / 13

v1.0.17

1 finding
LOW No provenance attestation provenance

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

v1.0.16

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.

v1.0.15

1 finding
LOW No provenance attestation provenance

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

v1.0.14

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.

v1.0.13

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.

v1.0.12

1 finding
LOW No provenance attestation provenance

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

v1.0.11

1 finding
LOW No provenance attestation provenance

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

v1.0.10

1 finding
LOW No provenance attestation provenance

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

v1.0.9

1 finding
LOW No provenance attestation provenance

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

v1.0.8

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.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.

v1.0.2

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.

v1.0.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.

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