← Home

@smarthivelabs-devs/auth-expo

SmartHive Auth provider, hooks, and SecureStore integration for React Native / Expo

32
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

smarthivelabskeldricklaurenkutah1

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): No malicious behavior tied to publish-env change; publisher has clean history. ai
publish-pattern new-deps-added AI (publish-pattern): jsrsasign is a standard crypto lib appropriate for an auth SDK. ai
provenance no-provenance AI (provenance): Low-signal for this package; no other risk indicators present. ai

Versions (showing 32 of 32)

Version Deps Published
1.11.6 2 / 8
1.11.5 2 / 8
1.11.4 2 / 8
1.11.3 2 / 8
1.11.2 2 / 8
1.11.1 2 / 8
1.11.0 2 / 8
1.10.1 2 / 8
1.10.0 2 / 8
1.9.0 1 / 8
1.7.6 1 / 8
1.7.5 1 / 8
1.7.4 1 / 9
1.7.3 1 / 9
1.7.2 1 / 9
1.7.1 1 / 9
1.7.0 1 / 9
1.6.7 1 / 9
1.6.6 1 / 9
1.6.5 1 / 9
1.6.4 1 / 9
1.6.3 1 / 9
1.6.2 0 / 9
1.6.1 0 / 7
1.6.0 0 / 7
1.5.0 0 / 6
1.4.0 0 / 6
1.3.0 0 / 6
1.2.0 0 / 5
1.1.0 0 / 5
1.0.0 0 / 5
0.1.0 0 / 5

v1.11.6

1 finding
INFO No provenance attestation provenance

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

v1.11.5

1 finding
INFO No provenance attestation provenance

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

v1.11.4

1 finding
INFO No provenance attestation provenance

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

v1.11.3

1 finding
INFO No provenance attestation provenance

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

v1.11.2

1 finding
INFO No provenance attestation provenance

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

v1.11.1

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: smarthivelabs.

v1.11.0

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: smarthivelabs.

v1.10.1

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: smarthivelabs.

v1.10.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: smarthivelabs.

INFO No provenance attestation provenance

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

v1.9.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: smarthivelabs.

INFO No provenance attestation provenance

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

v1.7.6

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: smarthivelabs.

INFO No provenance attestation provenance

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

v1.7.5

1 finding
INFO No provenance attestation provenance

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