@atlaskit/platform-feature-flags-react No license 18 versions

@atlaskit/platform-feature-flags-react

npm Repository Homepage

18

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.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@atlaskit/css	AI (phantom-deps): Atlassian monorepo pattern: dependencies declared for transitive consumption by consumers, not direct import.	ai	2026/04/26
phantom-deps	phantom-dep:@atlaskit/tokens	AI (phantom-deps): Atlassian monorepo pattern: dependencies declared for transitive consumption by consumers, not direct import.	ai	2026/04/26
phantom-deps	phantom-dep:@atlaskit/primitives	AI (phantom-deps): Atlassian monorepo pattern: dependencies declared for transitive consumption by consumers, not direct import.	ai	2026/04/26
bogus-package	bogus-package	AI (bogus-package): Atlassian internal monorepo utility package; minimal README and no keywords are expected for internal tooling packages, not spam indicators.	ai	2026/04/24
phantom-deps	phantom-dep:@compiled/react	AI (phantom-deps): @compiled/react is a build-time CSS-in-JS tool referenced in config; phantom dep finding is a stable false positive for Atlaskit packages using Compiled.	ai	2026/04/24
phantom-deps	phantom-dep:react-magnetic-di	AI (phantom-deps): react-magnetic-di referenced in config files for DI setup; stable false positive for this Atlaskit package.	ai	2026/04/24

Versions (showing 18 of 18)

Version	Deps	Published
0.5.1	4 / 8	2026-05-20
0.5.0	4 / 7	2026-05-13
0.4.4	4 / 7	2026-02-24
0.4.3	7 / 8	2025-11-24
0.4.2	7 / 8	2025-11-20
0.4.1	7 / 8	2025-11-07
0.4.0	7 / 8	2025-10-29
0.3.5	7 / 8	2025-10-16
0.3.4	7 / 8	2025-10-15
0.3.3	7 / 8	2025-10-13
0.3.2	7 / 8	2025-09-05
0.3.1	7 / 8	2025-09-04
0.3.0	7 / 8	2025-08-29
0.2.4	7 / 10	2025-08-04
0.2.3	7 / 10	2025-06-27
0.2.2	7 / 10	2025-06-19
0.2.1	7 / 10	2025-06-03
0.2.0	7 / 10	2025-05-08

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.4

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

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.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.4.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.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.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.2.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.