← Home

@docyrus/rn-assistant

npm Repository Homepage

Standalone React Native AI assistant package for Docyrus-compatible backends.

8
Versions
MIT
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

ardabeyazogluarzuecemanil.beyazogluerhan

Keywords

docyrusreact-nativeexpoassistantaichat

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): CI-published package; provenance absence is common and no other risk signals present. ai
phantom-deps phantom-dep:expo-constants AI (phantom-deps): expo-constants is declared as a dep and referenced in config; phantom-dep heuristic false positive for Expo packages. ai
phantom-deps phantom-dep:expo-file-system AI (phantom-deps): expo-file-system is declared as a dep and referenced in config; phantom-dep heuristic false positive for Expo packages. ai
phantom-deps phantom-dep:@types/turndown AI (phantom-deps): Type-only package; not imported at runtime, loaded by TypeScript convention. Stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
0.28.1 7 / 15
0.28.0 7 / 15
0.27.0 7 / 15
0.26.1 7 / 15
0.26.0 7 / 15
0.25.0 7 / 15
0.19.1 14 / 6
0.16.2 14 / 6

v0.28.1

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

1 finding
LOW No provenance attestation provenance

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

v0.26.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.25.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.19.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.16.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.