@contractspec/example.versioned-knowledge-base
Example: curated, versioned knowledge base with immutable sources, rule versions, and published snapshots.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@contractspec/lib.schema | AI (dependencies): Internal monorepo dependency from the same @contractspec namespace; consistent across versions. | ai | |
| dependencies | unvetted-dep:@contractspec/lib.contracts-spec | AI (dependencies): Internal monorepo dependency from the same @contractspec namespace; consistent across versions. | ai |
Versions (showing 51 of 81)
| Version | Deps | Published |
|---|---|---|
| 3.7.29 | 2 / 3 | |
| 3.7.28 | 2 / 3 | |
| 3.7.27 | 2 / 3 | |
| 3.7.26 | 2 / 3 | |
| 3.7.25 | 2 / 3 | |
| 3.7.24 | 2 / 3 | |
| 3.7.23 | 2 / 3 | |
| 3.7.22 | 2 / 3 | |
| 3.7.21 | 2 / 3 | |
| 3.7.20 | 2 / 3 | |
| 3.7.19 | 2 / 3 | |
| 3.7.18 | 2 / 3 | |
| 3.7.17 | 2 / 3 | |
| 3.7.16 | 2 / 3 | |
| 3.7.15 | 2 / 3 | |
| 3.7.14 | 2 / 3 | |
| 3.7.12 | 2 / 3 | |
| 3.7.10 | 2 / 3 | |
| 3.7.7 | 2 / 3 | |
| 3.7.6 | 2 / 3 | |
| 3.7.5 | 2 / 3 | |
| 3.7.4 | 2 / 3 | |
| 3.7.3 | 2 / 3 | |
| 3.7.1 | 2 / 3 | |
| 3.7.0 | 2 / 3 | |
| 3.6.0 | 2 / 3 | |
| 3.5.5 | 2 / 3 | |
| 3.5.4 | 2 / 3 | |
| 3.5.3 | 2 / 3 | |
| 3.5.2 | 2 / 3 | |
| 3.5.0 | 2 / 3 | |
| 3.4.3 | 2 / 3 | |
| 3.4.2 | 2 / 3 | |
| 3.4.1 | 2 / 3 | |
| 3.4.0 | 2 / 3 | |
| 3.3.0 | 2 / 3 | |
| 3.2.0 | 2 / 3 | |
| 3.1.1 | 2 / 3 | |
| 3.0.0 | 2 / 3 | |
| 2.9.1 | 2 / 3 | |
| 2.9.0 | 2 / 3 | |
| 2.8.0 | 2 / 3 | |
| 2.7.0 | 2 / 3 | |
| 2.6.0 | 2 / 3 | |
| 2.5.0 | 2 / 3 | |
| 2.4.0 | 2 / 3 | |
| 2.3.0 | 2 / 3 | |
| 2.2.0 | 2 / 3 | |
| 2.1.1 | 2 / 3 | |
| 2.1.0 | 2 / 3 | |
| 2.0.0 | 2 / 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.