@contractspec/lib.presentation-runtime-react-native
React Native presentation runtime for mobile apps
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 51 of 77)
| Version | Deps | Published |
|---|---|---|
| 40.0.3 | 5 / 2 | |
| 40.0.2 | 5 / 2 | |
| 40.0.1 | 5 / 2 | |
| 40.0.0 | 5 / 2 | |
| 39.0.1 | 5 / 2 | |
| 39.0.0 | 5 / 2 | |
| 38.0.3 | 5 / 2 | |
| 38.0.2 | 5 / 2 | |
| 38.0.1 | 5 / 2 | |
| 38.0.0 | 5 / 2 | |
| 36.0.7 | 4 / 2 | |
| 36.0.6 | 4 / 2 | |
| 36.0.5 | 4 / 2 | |
| 36.0.4 | 4 / 2 | |
| 36.0.3 | 4 / 2 | |
| 36.0.2 | 4 / 2 | |
| 36.0.1 | 4 / 2 | |
| 36.0.0 | 4 / 2 | |
| 35.0.3 | 4 / 2 | |
| 35.0.0 | 4 / 2 | |
| 34.0.6 | 2 / 2 | |
| 34.0.5 | 2 / 2 | |
| 34.0.4 | 2 / 2 | |
| 34.0.3 | 2 / 2 | |
| 34.0.1 | 2 / 2 | |
| 34.0.0 | 2 / 2 | |
| 33.0.0 | 2 / 2 | |
| 32.0.5 | 2 / 2 | |
| 32.0.4 | 2 / 2 | |
| 32.0.3 | 2 / 2 | |
| 32.0.2 | 2 / 2 | |
| 32.0.0 | 2 / 2 | |
| 31.0.3 | 2 / 2 | |
| 31.0.2 | 2 / 2 | |
| 31.0.1 | 2 / 2 | |
| 31.0.0 | 2 / 2 | |
| 30.0.0 | 2 / 2 | |
| 29.0.0 | 2 / 2 | |
| 28.0.1 | 2 / 2 | |
| 27.0.0 | 2 / 2 | |
| 26.0.0 | 2 / 2 | |
| 25.0.0 | 2 / 2 | |
| 24.0.0 | 2 / 2 | |
| 23.0.0 | 2 / 2 | |
| 22.0.0 | 2 / 2 | |
| 21.0.0 | 2 / 2 | |
| 20.0.0 | 2 / 2 | |
| 19.0.0 | 2 / 2 | |
| 18.0.0 | 2 / 2 | |
| 17.0.0 | 2 / 2 | |
| 16.0.0 | 2 / 2 |
v40.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v40.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v40.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v36.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v36.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v36.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v36.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v36.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v35.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v35.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v34.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v34.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v34.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v34.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v34.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v34.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.