@contractspec/example.crm-pipeline
CRM Pipeline - Contacts, Companies, Deals, Tasks
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:zod | AI (phantom-deps): Config-file usage is legitimate; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.bus | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.jobs | AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is explicitly declared in dependencies; phantom-dep fires because it's referenced via config rather than direct import. | ai |
Versions (showing 51 of 84)
| Version | Deps | Published |
|---|---|---|
| 3.7.33 | 13 / 6 | |
| 3.7.32 | 13 / 6 | |
| 3.7.31 | 13 / 6 | |
| 3.7.30 | 13 / 6 | |
| 3.7.29 | 13 / 6 | |
| 3.7.28 | 12 / 6 | |
| 3.7.27 | 12 / 6 | |
| 3.7.26 | 12 / 6 | |
| 3.7.25 | 12 / 6 | |
| 3.7.24 | 12 / 6 | |
| 3.7.23 | 12 / 6 | |
| 3.7.22 | 12 / 6 | |
| 3.7.20 | 12 / 6 | |
| 3.7.19 | 12 / 6 | |
| 3.7.18 | 12 / 6 | |
| 3.7.17 | 12 / 6 | |
| 3.7.16 | 12 / 6 | |
| 3.7.15 | 12 / 6 | |
| 3.7.14 | 12 / 6 | |
| 3.7.12 | 12 / 6 | |
| 3.7.10 | 11 / 6 | |
| 3.7.7 | 11 / 5 | |
| 3.7.6 | 11 / 5 | |
| 3.7.5 | 11 / 5 | |
| 3.7.4 | 11 / 5 | |
| 3.7.3 | 11 / 5 | |
| 3.7.1 | 11 / 5 | |
| 3.7.0 | 11 / 5 | |
| 3.6.0 | 11 / 5 | |
| 3.5.5 | 11 / 5 | |
| 3.5.4 | 11 / 5 | |
| 3.5.3 | 11 / 5 | |
| 3.5.2 | 11 / 5 | |
| 3.5.0 | 11 / 5 | |
| 3.4.3 | 11 / 5 | |
| 3.4.2 | 11 / 5 | |
| 3.4.1 | 11 / 5 | |
| 3.4.0 | 11 / 5 | |
| 3.3.0 | 11 / 5 | |
| 3.2.0 | 11 / 5 | |
| 3.1.1 | 11 / 5 | |
| 3.0.0 | 11 / 5 | |
| 2.9.1 | 11 / 5 | |
| 2.9.0 | 11 / 5 | |
| 2.8.0 | 11 / 5 | |
| 2.7.0 | 11 / 5 | |
| 2.6.1 | 11 / 5 | |
| 2.6.0 | 11 / 5 | |
| 2.5.0 | 11 / 5 | |
| 2.4.0 | 11 / 5 | |
| 2.3.0 | 11 / 5 |
v3.7.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.30
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.1
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.