@openfeature/server-sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.22.0 | 0 / 1 | |
| 1.21.0 | 0 / 1 | |
| 1.20.2 | 0 / 1 | |
| 1.20.1 | 0 / 1 | |
| 1.20.0 | 0 / 1 | |
| 1.19.0 | 0 / 1 | |
| 1.18.0 | 0 / 1 | |
| 1.17.1 | 0 / 1 | |
| 1.17.0 | 0 / 1 | |
| 1.16.2 | 0 / 1 | |
| 1.16.1 | 0 / 1 | |
| 1.16.0 | 0 / 1 | |
| 1.15.1 | 0 / 1 | |
| 1.15.0 | 0 / 1 | |
| 1.14.0 | 0 / 1 | |
| 1.13.5 | 0 / 1 | |
| 1.13.4 | 0 / 1 | |
| 1.13.3 | 0 / 1 | |
| 1.13.2 | 0 / 1 | |
| 1.13.1 | 0 / 1 | |
| 1.13.0 | 0 / 1 | |
| 1.12.0 | 0 / 1 | |
| 1.11.0 | 0 / 1 | |
| 1.10.0 | 0 / 1 | |
| 1.9.1 | 0 / 1 | |
| 1.9.0 | 0 / 1 | |
| 1.8.0 | 0 / 1 | |
| 1.7.5 | 0 / 1 | |
| 1.7.4 | 0 / 1 | |
| 1.7.3 | 0 / 1 | |
| 1.7.2 | 0 / 1 | |
| 1.7.1 | 0 / 1 | |
| 1.7.0 | 0 / 1 | |
| 1.6.3 | 0 / 1 | |
| 1.6.2 | 0 / 1 |
v1.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.