@or-sdk/contacts
Supply chain provenance
Status for the latest visible version.
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
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 4.7.3 | 4 / 3 | |
| 4.7.2 | 4 / 3 | |
| 4.7.1 | 4 / 3 | |
| 4.7.0 | 4 / 3 | |
| 4.6.5 | 4 / 3 | |
| 4.6.4 | 4 / 3 | |
| 4.6.3 | 4 / 4 | |
| 4.6.2 | 4 / 4 | |
| 4.6.1 | 4 / 4 | |
| 4.6.0 | 4 / 4 | |
| 4.5.22 | 4 / 7 | |
| 4.5.21 | 4 / 7 | |
| 4.5.20 | 4 / 7 | |
| 4.5.19 | 4 / 7 | |
| 4.5.18 | 4 / 7 | |
| 4.5.17 | 4 / 7 | |
| 4.5.16 | 4 / 7 | |
| 4.5.15 | 4 / 7 | |
| 4.5.14 | 4 / 7 | |
| 4.5.13 | 4 / 7 | |
| 4.5.12 | 4 / 7 | |
| 4.5.11 | 4 / 7 | |
| 4.5.10 | 4 / 7 | |
| 4.5.9 | 4 / 7 | |
| 4.5.8 | 4 / 7 | |
| 4.5.7 | 4 / 7 | |
| 4.5.6 | 4 / 7 | |
| 4.5.5 | 4 / 7 | |
| 4.5.4 | 4 / 7 | |
| 4.5.3 | 4 / 7 | |
| 4.5.2 | 4 / 7 |
v4.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.