@contractspec/lib.ai-providers
Unified AI provider abstraction layer
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:zod | AI (phantom-deps): Declared as peer/optional dep for config validation; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google | AI (phantom-deps): AI SDK providers declared as deps but loaded dynamically via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): AI SDK providers declared as deps but loaded dynamically via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/mistral | AI (phantom-deps): AI SDK providers declared as deps but loaded dynamically via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/anthropic | AI (phantom-deps): AI SDK providers declared as deps but loaded dynamically via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:ollama-ai-provider | AI (phantom-deps): AI SDK providers declared as deps but loaded dynamically via config; stable false positive. | ai |
Versions (showing 74 of 74)
| Version | Deps | Published |
|---|---|---|
| 3.7.22 | 9 / 3 | |
| 3.7.21 | 9 / 3 | |
| 3.7.20 | 9 / 3 | |
| 3.7.19 | 9 / 3 | |
| 3.7.18 | 9 / 3 | |
| 3.7.17 | 9 / 3 | |
| 3.7.16 | 9 / 3 | |
| 3.7.15 | 9 / 3 | |
| 3.7.14 | 9 / 3 | |
| 3.7.13 | 8 / 3 | |
| 3.7.12 | 8 / 3 | |
| 3.7.11 | 8 / 3 | |
| 3.7.10 | 8 / 3 | |
| 3.7.9 | 8 / 3 | |
| 3.7.8 | 8 / 3 | |
| 3.7.6 | 8 / 3 | |
| 3.7.5 | 8 / 3 | |
| 3.7.4 | 8 / 3 | |
| 3.7.3 | 8 / 3 | |
| 3.7.1 | 8 / 3 | |
| 3.7.0 | 8 / 3 | |
| 3.6.0 | 8 / 3 | |
| 3.5.5 | 8 / 3 | |
| 3.5.4 | 8 / 3 | |
| 3.5.3 | 8 / 3 | |
| 3.5.2 | 8 / 3 | |
| 3.5.0 | 8 / 3 | |
| 3.4.3 | 8 / 3 | |
| 3.4.2 | 8 / 3 | |
| 3.4.1 | 8 / 3 | |
| 3.4.0 | 8 / 3 | |
| 3.3.0 | 8 / 3 | |
| 3.2.0 | 8 / 3 | |
| 3.1.1 | 8 / 3 | |
| 3.0.0 | 7 / 3 | |
| 2.9.0 | 7 / 3 | |
| 2.8.0 | 7 / 3 | |
| 2.7.0 | 7 / 3 | |
| 2.6.0 | 7 / 3 | |
| 2.5.0 | 7 / 3 | |
| 2.4.0 | 7 / 3 | |
| 2.3.0 | 7 / 3 | |
| 2.2.0 | 7 / 3 | |
| 2.1.0 | 7 / 3 | |
| 2.0.0 | 7 / 3 | |
| 1.62.0 | 7 / 3 | |
| 1.61.0 | 7 / 3 | |
| 1.60.0 | 7 / 3 | |
| 1.59.0 | 7 / 3 | |
| 1.58.0 | 7 / 3 | |
| 1.57.0 | 7 / 4 | |
| 1.56.1 | 7 / 4 | |
| 1.56.0 | 7 / 4 | |
| 1.55.0 | 7 / 4 | |
| 1.54.0 | 7 / 4 | |
| 1.53.0 | 7 / 4 | |
| 1.52.0 | 7 / 4 | |
| 1.51.0 | 7 / 4 | |
| 1.50.0 | 7 / 4 | |
| 1.49.0 | 7 / 4 | |
| 1.48.0 | 7 / 4 | |
| 1.47.0 | 7 / 4 | |
| 1.46.2 | 7 / 4 | |
| 1.46.1 | 7 / 4 | |
| 1.46.0 | 7 / 4 | |
| 1.45.6 | 7 / 4 | |
| 1.45.5 | 7 / 4 | |
| 1.45.4 | 7 / 4 | |
| 1.45.3 | 7 / 4 | |
| 1.45.2 | 7 / 4 | |
| 1.45.1 | 7 / 4 | |
| 1.45.0 | 7 / 4 | |
| 1.44.1 | 7 / 4 | |
| 1.44.0 | 7 / 4 |
v3.7.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.21
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.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.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.8
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.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.
v1.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.