@contractspec/lib.support-bot
AI support bot framework with RAG and ticket management
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:@contractspec/lib.schema | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic fires on bundled monorepo packages routinely. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Referenced in config files as peer/type dep; stable false positive for this package. | ai |
Versions (showing 51 of 81)
| Version | Deps | Published |
|---|---|---|
| 4.0.9 | 6 / 3 | |
| 4.0.8 | 6 / 3 | |
| 4.0.7 | 6 / 3 | |
| 4.0.6 | 6 / 3 | |
| 4.0.5 | 6 / 3 | |
| 4.0.4 | 6 / 3 | |
| 4.0.3 | 6 / 3 | |
| 4.0.2 | 6 / 3 | |
| 4.0.1 | 6 / 3 | |
| 4.0.0 | 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 | 7 / 3 | |
| 3.7.7 | 7 / 3 | |
| 3.7.6 | 7 / 3 | |
| 3.7.5 | 7 / 3 | |
| 3.7.4 | 7 / 3 | |
| 3.7.3 | 7 / 3 | |
| 3.7.1 | 7 / 3 | |
| 3.7.0 | 7 / 3 | |
| 3.6.0 | 7 / 3 | |
| 3.5.5 | 7 / 3 | |
| 3.5.4 | 7 / 3 | |
| 3.5.3 | 7 / 3 | |
| 3.5.2 | 7 / 3 | |
| 3.5.0 | 7 / 3 | |
| 3.4.3 | 7 / 3 | |
| 3.4.2 | 7 / 3 | |
| 3.4.1 | 7 / 3 | |
| 3.4.0 | 7 / 3 | |
| 3.3.0 | 7 / 3 | |
| 3.2.0 | 7 / 3 | |
| 3.1.1 | 7 / 3 | |
| 3.0.0 | 7 / 3 | |
| 2.9.1 | 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.1 | 7 / 3 | |
| 2.1.0 | 7 / 3 | |
| 2.0.0 | 7 / 3 |
v4.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.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.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.