@contractspec/app.cli-database
Website: https://contractspec.io
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:execa | AI (phantom-deps): CLI tool; execa used indirectly via database command delegation. | ai | |
| phantom-deps | phantom-dep:minimist | AI (phantom-deps): CLI tool; minimist used indirectly via database command delegation. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.schema | AI (phantom-deps): Same-org scoped dep; used indirectly via database command delegation. | ai | |
| phantom-deps | phantom-dep:@prisma/client | AI (phantom-deps): Prisma client is a config-driven dependency; referenced in Prisma schema, not direct imports. | ai | |
| phantom-deps | phantom-dep:@prisma/adapter-pg | AI (phantom-deps): Prisma adapter is config-driven; referenced in Prisma schema, not direct imports. | ai | |
| phantom-deps | phantom-dep:prisma | AI (phantom-deps): prisma is a CLI tool dependency invoked via execa/bin, not imported directly; phantom-dep is a stable false positive here. | ai |
Versions (showing 51 of 75)
| Version | Deps | Published |
|---|---|---|
| 3.7.24 | 5 / 4 | |
| 3.7.23 | 5 / 4 | |
| 3.7.22 | 5 / 4 | |
| 3.7.21 | 5 / 4 | |
| 3.7.20 | 5 / 4 | |
| 3.7.19 | 5 / 4 | |
| 3.7.18 | 5 / 4 | |
| 3.7.17 | 5 / 4 | |
| 3.7.16 | 5 / 4 | |
| 3.7.15 | 4 / 4 | |
| 3.7.14 | 4 / 4 | |
| 3.7.13 | 4 / 4 | |
| 3.7.12 | 4 / 4 | |
| 3.7.11 | 4 / 4 | |
| 3.7.9 | 4 / 4 | |
| 3.7.7 | 4 / 4 | |
| 3.7.6 | 4 / 4 | |
| 3.7.5 | 4 / 4 | |
| 3.7.4 | 4 / 4 | |
| 3.7.3 | 4 / 4 | |
| 3.7.1 | 4 / 4 | |
| 3.7.0 | 4 / 4 | |
| 3.6.0 | 4 / 4 | |
| 3.5.5 | 4 / 4 | |
| 3.5.4 | 4 / 4 | |
| 3.5.3 | 4 / 4 | |
| 3.5.2 | 4 / 4 | |
| 3.5.0 | 4 / 4 | |
| 3.4.3 | 4 / 4 | |
| 3.4.2 | 4 / 4 | |
| 3.4.1 | 4 / 4 | |
| 3.4.0 | 4 / 4 | |
| 3.3.0 | 4 / 4 | |
| 3.2.0 | 4 / 4 | |
| 3.1.0 | 4 / 4 | |
| 3.0.0 | 4 / 4 | |
| 2.9.0 | 4 / 4 | |
| 2.8.0 | 4 / 4 | |
| 2.7.0 | 4 / 4 | |
| 2.6.0 | 4 / 4 | |
| 2.5.0 | 4 / 4 | |
| 2.4.0 | 4 / 4 | |
| 2.3.0 | 4 / 4 | |
| 2.2.0 | 4 / 4 | |
| 2.1.0 | 4 / 4 | |
| 2.0.0 | 4 / 4 | |
| 1.62.0 | 4 / 4 | |
| 1.61.0 | 4 / 4 | |
| 1.60.0 | 4 / 4 | |
| 1.59.0 | 4 / 4 | |
| 1.58.0 | 4 / 4 |
v3.7.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.23
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.13
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.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.9
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.0
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.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.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.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.