@contractspec/lib.contracts-transformers
Contract format transformations: import/export between ContractSpec and external formats (OpenAPI, AsyncAPI, etc.)
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): yaml is a legitimate declared runtime dep; phantom-dep fires because it's not directly imported in analyzed entry points. | ai | |
| phantom-deps | phantom-dep:compare-versions | AI (phantom-deps): compare-versions is a legitimate declared runtime dep; same phantom-dep false positive pattern. | ai |
Versions (showing 51 of 81)
| Version | Deps | Published |
|---|---|---|
| 3.7.29 | 6 / 3 | |
| 3.7.28 | 6 / 3 | |
| 3.7.27 | 6 / 3 | |
| 3.7.26 | 6 / 3 | |
| 3.7.25 | 6 / 3 | |
| 3.7.24 | 6 / 3 | |
| 3.7.23 | 6 / 3 | |
| 3.7.22 | 6 / 3 | |
| 3.7.21 | 6 / 3 | |
| 3.7.20 | 6 / 3 | |
| 3.7.19 | 6 / 3 | |
| 3.7.18 | 6 / 3 | |
| 3.7.17 | 6 / 3 | |
| 3.7.16 | 6 / 3 | |
| 3.7.15 | 6 / 3 | |
| 3.7.14 | 6 / 3 | |
| 3.7.12 | 6 / 3 | |
| 3.7.10 | 6 / 3 | |
| 3.7.7 | 6 / 3 | |
| 3.7.6 | 6 / 3 | |
| 3.7.5 | 6 / 3 | |
| 3.7.4 | 6 / 3 | |
| 3.7.3 | 6 / 3 | |
| 3.7.1 | 6 / 3 | |
| 3.7.0 | 6 / 3 | |
| 3.6.0 | 6 / 3 | |
| 3.5.5 | 6 / 3 | |
| 3.5.4 | 6 / 3 | |
| 3.5.3 | 6 / 3 | |
| 3.5.2 | 6 / 3 | |
| 3.5.0 | 6 / 3 | |
| 3.4.3 | 6 / 3 | |
| 3.4.2 | 6 / 3 | |
| 3.4.1 | 6 / 3 | |
| 3.4.0 | 6 / 3 | |
| 3.3.0 | 6 / 3 | |
| 3.2.0 | 6 / 3 | |
| 3.1.1 | 6 / 3 | |
| 3.0.0 | 6 / 3 | |
| 2.9.1 | 6 / 3 | |
| 2.9.0 | 6 / 3 | |
| 2.8.0 | 6 / 3 | |
| 2.7.0 | 6 / 3 | |
| 2.6.0 | 6 / 3 | |
| 2.5.0 | 6 / 3 | |
| 2.4.0 | 6 / 3 | |
| 2.3.0 | 6 / 3 | |
| 2.2.0 | 6 / 3 | |
| 2.1.1 | 6 / 3 | |
| 2.1.0 | 6 / 3 | |
| 2.0.0 | 6 / 3 |
v3.7.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.