← Home

@vitality-ds/components-react-native

npm Repository Homepage

Deliver world-class digital health experiences with ease on mobile.

14
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

lucas.arundellgeniesolutionsadminxanderangelladrianaheeshxiaochi-limag-ken-sully

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@babel/preset-typescript AI (phantom-deps): Framework-scoped package loaded by Babel convention; stable pattern. ai
phantom-deps phantom-dep:@testing-library/react-native AI (phantom-deps): Testing framework loaded by convention; stable pattern. ai
phantom-deps phantom-dep:@vitality-ds/tokens AI (phantom-deps): Same-org dependency; likely loaded via re-export or convention. ai
phantom-deps phantom-dep:@vitality-ds/icons-react-native AI (phantom-deps): Same-org dependency; likely loaded via re-export or convention. ai

Versions (showing 14 of 14)

Version Deps Published
5.6.3 9 / 22
5.6.2 9 / 22
5.6.1 9 / 22
5.6.0 9 / 22
5.5.0 9 / 22
5.4.0 9 / 22
5.3.0 9 / 22
5.2.1 9 / 22
5.2.0 9 / 22
5.1.1 9 / 22
5.1.0 9 / 22
5.0.4 9 / 22
5.0.3 9 / 22
5.0.2 9 / 22

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

v5.6.2

1 finding
LOW No provenance attestation provenance

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

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

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

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

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

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

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

v5.2.0

1 finding
LOW No provenance attestation provenance

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

v5.1.1

1 finding
LOW No provenance attestation provenance

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

v5.1.0

1 finding
LOW No provenance attestation provenance

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

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

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

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