@contractspec/example.marketplace
Marketplace example with orders, payouts, and reviews for ContractSpec
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:@contractspec/module.notifications | AI (phantom-deps): Same-org scoped dep; monorepo transitive usage pattern. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.metering | AI (phantom-deps): Same-org scoped dep; monorepo transitive usage pattern. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.identity-rbac | AI (phantom-deps): Same-org scoped dep; monorepo transitive usage pattern. | ai | |
| phantom-deps | phantom-dep:@contractspec/module.audit-trail | AI (phantom-deps): Same-org scoped dep; monorepo transitive usage pattern. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared and used transitively; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.bus | AI (phantom-deps): Same-org scoped dep; monorepo transitive usage pattern. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.jobs | AI (phantom-deps): Same-org scoped dep; monorepo transitive usage pattern. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.files | AI (phantom-deps): Same-org scoped dep; monorepo transitive usage pattern. | ai | |
| dependencies | unvetted-dep:@contractspec/lib.design-system | AI (dependencies): Same-org scoped dependency within the contractspec monorepo; consistent pattern across package versions. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.example-shared-ui | AI (phantom-deps): Same-org scope dep; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer/runtime dep declared in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 84 of 84)
| Version | Deps | Published |
|---|---|---|
| 3.8.25 | 8 / 5 | |
| 3.8.24 | 8 / 5 | |
| 3.8.23 | 8 / 5 | |
| 3.8.22 | 8 / 5 | |
| 3.8.21 | 8 / 5 | |
| 3.8.20 | 8 / 5 | |
| 3.8.19 | 8 / 5 | |
| 3.8.18 | 8 / 5 | |
| 3.8.17 | 8 / 5 | |
| 3.8.16 | 8 / 5 | |
| 3.8.15 | 8 / 5 | |
| 3.8.14 | 8 / 5 | |
| 3.8.12 | 8 / 5 | |
| 3.8.11 | 8 / 5 | |
| 3.8.10 | 8 / 5 | |
| 3.8.9 | 8 / 5 | |
| 3.8.8 | 8 / 5 | |
| 3.8.7 | 8 / 5 | |
| 3.8.6 | 8 / 5 | |
| 3.8.4 | 8 / 5 | |
| 3.8.2 | 7 / 5 | |
| 3.7.7 | 7 / 5 | |
| 3.7.6 | 7 / 5 | |
| 3.7.5 | 7 / 5 | |
| 3.7.4 | 7 / 5 | |
| 3.7.3 | 7 / 5 | |
| 3.7.1 | 7 / 5 | |
| 3.7.0 | 7 / 5 | |
| 3.6.0 | 7 / 5 | |
| 3.5.5 | 7 / 5 | |
| 3.5.4 | 7 / 5 | |
| 3.5.3 | 7 / 5 | |
| 3.5.2 | 7 / 5 | |
| 3.5.0 | 7 / 5 | |
| 3.4.3 | 7 / 5 | |
| 3.4.2 | 7 / 5 | |
| 3.4.1 | 7 / 5 | |
| 3.4.0 | 7 / 5 | |
| 3.3.0 | 7 / 5 | |
| 3.2.0 | 7 / 5 | |
| 3.1.1 | 7 / 5 | |
| 3.0.0 | 7 / 5 | |
| 2.9.1 | 7 / 5 | |
| 2.9.0 | 7 / 5 | |
| 2.8.0 | 7 / 5 | |
| 2.7.0 | 7 / 5 | |
| 2.6.1 | 7 / 5 | |
| 2.6.0 | 7 / 5 | |
| 2.5.0 | 7 / 5 | |
| 2.4.0 | 7 / 5 | |
| 2.3.0 | 7 / 5 | |
| 2.2.0 | 7 / 5 | |
| 2.1.1 | 7 / 5 | |
| 2.1.0 | 7 / 5 | |
| 2.0.0 | 7 / 5 | |
| 1.62.0 | 7 / 5 | |
| 1.61.0 | 7 / 5 | |
| 1.60.0 | 7 / 5 | |
| 1.59.0 | 7 / 5 | |
| 1.58.0 | 7 / 5 | |
| 1.57.0 | 7 / 5 | |
| 1.56.1 | 7 / 5 | |
| 1.56.0 | 7 / 5 | |
| 1.55.0 | 7 / 5 | |
| 1.54.0 | 7 / 5 | |
| 1.53.0 | 7 / 5 | |
| 1.52.0 | 7 / 5 | |
| 1.51.0 | 7 / 5 | |
| 1.50.0 | 7 / 5 | |
| 1.49.0 | 7 / 5 | |
| 1.48.1 | 7 / 5 | |
| 1.48.0 | 7 / 5 | |
| 1.47.0 | 7 / 5 | |
| 1.46.1 | 2 / 3 | |
| 1.46.0 | 2 / 3 | |
| 1.45.6 | 2 / 3 | |
| 1.45.5 | 2 / 3 | |
| 1.45.4 | 2 / 3 | |
| 1.45.3 | 2 / 3 | |
| 1.45.2 | 2 / 3 | |
| 1.45.1 | 10 / 3 | |
| 1.45.0 | 10 / 3 | |
| 1.44.1 | 10 / 3 | |
| 1.44.0 | 10 / 3 |
v3.8.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.2
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.
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.
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.1
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.