@contractspec/example.integration-hub
Integration Hub example with sync engine and field mappings 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.audit-trail | AI (phantom-deps): Declared and used indirectly via re-exports; same-org scope pattern. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.identity-rbac | AI (phantom-deps): Declared and used indirectly via re-exports; same-org scope pattern. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.feature-flags | AI (phantom-deps): Declared and used indirectly via re-exports; same-org scope pattern. | ai | |
| phantom-deps | phantom-dep:@contractspec/module.notifications | AI (phantom-deps): Declared and used indirectly via re-exports; same-org scope pattern. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared and used indirectly; heuristic false positive in this monorepo. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.bus | AI (phantom-deps): Declared and used indirectly via re-exports; same-org scope pattern. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.jobs | AI (phantom-deps): Declared and used indirectly via re-exports; same-org scope pattern. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.files | AI (phantom-deps): Declared and used indirectly via re-exports; same-org scope pattern. | ai | |
| source-diff | obfuscated-file:dist/ui/IntegrationHubCredentialSetupPreview.js | AI (source-diff): Bun-bundled minified output; // @bun header confirms standard build artifact. | ai | |
| source-diff | obfuscated-file:dist/node/setup/credential-setup.js | AI (source-diff): Bun-bundled minified output; // @bun header and readable config content confirm standard build artifact. | ai | |
| source-diff | obfuscated-file:dist/node/setup/index.js | AI (source-diff): Bun-bundled minified output; consistent with package build toolchain. | ai | |
| source-diff | obfuscated-file:dist/node/ui/IntegrationHubCredentialSetupPreview.js | AI (source-diff): Bun-bundled minified output; consistent with package build toolchain. | ai | |
| source-diff | obfuscated-file:dist/node/ui/IntegrationHubCredentialSetupPreview.model.js | AI (source-diff): Bun-bundled minified output; consistent with package build toolchain. | ai | |
| source-diff | obfuscated-file:dist/setup/credential-setup.js | AI (source-diff): Bun-bundled minified output; // @bun header confirms standard build artifact. | ai | |
| source-diff | obfuscated-file:dist/setup/index.js | AI (source-diff): Bun-bundled minified output; // @bun header confirms standard build artifact. | ai | |
| source-diff | obfuscated-file:dist/ui/IntegrationHubCredentialSetupPreview.model.js | AI (source-diff): Bun-bundled minified output; // @bun header confirms standard build artifact. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom declared as peer/config dep in a React package; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.example-shared-ui | AI (phantom-deps): Same-org monorepo dep; phantom pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@contractspec/module.ai-chat | AI (phantom-deps): Same-org monorepo dep; phantom pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.ui-kit-web | AI (phantom-deps): Same-org monorepo dep; phantom pattern is stable for this package. | ai |
Versions (showing 51 of 85)
| Version | Deps | Published |
|---|---|---|
| 3.9.2 | 13 / 6 | |
| 3.9.1 | 13 / 6 | |
| 3.9.0 | 13 / 6 | |
| 3.8.22 | 12 / 6 | |
| 3.8.21 | 12 / 6 | |
| 3.8.20 | 10 / 6 | |
| 3.8.19 | 10 / 6 | |
| 3.8.18 | 10 / 6 | |
| 3.8.17 | 10 / 6 | |
| 3.8.16 | 10 / 6 | |
| 3.8.15 | 10 / 6 | |
| 3.8.14 | 10 / 6 | |
| 3.8.12 | 10 / 6 | |
| 3.8.11 | 10 / 6 | |
| 3.8.10 | 10 / 6 | |
| 3.8.9 | 10 / 6 | |
| 3.8.8 | 10 / 6 | |
| 3.8.7 | 10 / 6 | |
| 3.8.6 | 10 / 6 | |
| 3.8.4 | 10 / 6 | |
| 3.8.2 | 9 / 6 | |
| 3.7.7 | 9 / 5 | |
| 3.7.6 | 9 / 5 | |
| 3.7.5 | 9 / 5 | |
| 3.7.4 | 9 / 5 | |
| 3.7.3 | 9 / 5 | |
| 3.7.1 | 9 / 5 | |
| 3.7.0 | 9 / 5 | |
| 3.6.0 | 9 / 5 | |
| 3.5.5 | 8 / 5 | |
| 3.5.4 | 8 / 5 | |
| 3.5.3 | 8 / 5 | |
| 3.5.2 | 8 / 5 | |
| 3.5.0 | 8 / 5 | |
| 3.4.3 | 8 / 5 | |
| 3.4.2 | 8 / 5 | |
| 3.4.1 | 8 / 5 | |
| 3.4.0 | 8 / 5 | |
| 3.3.0 | 8 / 5 | |
| 3.2.0 | 8 / 5 | |
| 3.1.1 | 8 / 5 | |
| 3.0.0 | 8 / 5 | |
| 2.9.1 | 8 / 5 | |
| 2.9.0 | 8 / 5 | |
| 2.8.0 | 8 / 5 | |
| 2.7.0 | 8 / 5 | |
| 2.6.1 | 8 / 5 | |
| 2.6.0 | 7 / 5 | |
| 2.5.0 | 7 / 5 | |
| 2.4.0 | 7 / 5 | |
| 2.3.0 | 7 / 5 |
v3.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.1
9 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
9 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.22
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.