@contractspec/lib.personalization
Behavior tracking, analysis, and adaptation helpers for ContractSpec personalization.
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:@opentelemetry/api | AI (phantom-deps): Declared as peer dependency; referenced in config but not directly imported is expected. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.bus | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic false positive in this context. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.schema | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic false positive in this context. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.knowledge | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic false positive in this context. | ai |
Versions (showing 51 of 81)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 6 / 3 | |
| 6.1.1 | 6 / 3 | |
| 6.1.0 | 6 / 3 | |
| 6.0.26 | 6 / 3 | |
| 6.0.25 | 6 / 3 | |
| 6.0.24 | 6 / 3 | |
| 6.0.23 | 6 / 3 | |
| 6.0.22 | 6 / 3 | |
| 6.0.21 | 6 / 3 | |
| 6.0.20 | 6 / 3 | |
| 6.0.19 | 6 / 3 | |
| 6.0.18 | 6 / 3 | |
| 6.0.17 | 6 / 3 | |
| 6.0.16 | 6 / 3 | |
| 6.0.15 | 6 / 3 | |
| 6.0.14 | 6 / 3 | |
| 6.0.12 | 6 / 3 | |
| 6.0.10 | 6 / 3 | |
| 6.0.7 | 6 / 3 | |
| 6.0.6 | 6 / 3 | |
| 6.0.5 | 6 / 3 | |
| 6.0.4 | 6 / 3 | |
| 6.0.3 | 6 / 3 | |
| 6.0.1 | 6 / 3 | |
| 6.0.0 | 6 / 3 | |
| 5.0.0 | 6 / 3 | |
| 4.0.5 | 6 / 3 | |
| 4.0.4 | 6 / 3 | |
| 4.0.3 | 6 / 3 | |
| 4.0.2 | 6 / 3 | |
| 4.0.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 |
v6.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.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.