@contractspec/lib.contracts-spec
Spec definitions and registries for ContractSpec
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/workflow/workflow-sdk.js | AI (source-diff): Bun-bundled dist output; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/contracts-spec.feature.js | AI (source-diff): Bun-bundled dist output; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/node/contracts-spec.feature.js | AI (source-diff): Bun-bundled dist output; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/node/results/index.js | AI (source-diff): Bun-bundled dist output; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/node/themes.validation.js | AI (source-diff): Bun-bundled dist output; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/node/workflow/workflow-sdk.js | AI (source-diff): Bun-bundled dist output; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/results/index.js | AI (source-diff): Bun-bundled dist output; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/themes.validation.js | AI (source-diff): Bun-bundled dist output; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/workspace-config/environment.js | AI (source-diff): Bun bundler minified output; content is zod-based env validation logic. | ai | |
| source-diff | obfuscated-file:dist/node/knowledge/registry.js | AI (source-diff): Bun bundler minified output; identical registry content to ESM variant. | ai | |
| source-diff | obfuscated-file:dist/node/workspace-config/environment.js | AI (source-diff): Bun bundler minified output; content is zod-based env validation logic. | ai | |
| source-diff | obfuscated-file:dist/knowledge/operation-models.js | AI (source-diff): Bun bundler minified output; content is schema definitions, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/knowledge/registry.js | AI (source-diff): Bun bundler minified output; content is registry/filter utilities, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/node/knowledge/operation-models.js | AI (source-diff): Bun bundler minified output; identical schema content to ESM variant. | ai | |
| phantom-deps | phantom-dep:@formatjs/icu-messageformat-parser | AI (phantom-deps): Declared in package.json deps but used indirectly via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:compare-versions | AI (phantom-deps): Declared in package.json deps but used indirectly via config; stable false positive for this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 6.4.0 | 4 / 3 | |
| 6.3.0 | 4 / 3 | |
| 6.2.0 | 4 / 3 | |
| 6.1.0 | 3 / 3 | |
| 6.0.0 | 3 / 3 | |
| 5.7.0 | 3 / 3 | |
| 5.6.0 | 3 / 3 | |
| 5.5.1 | 3 / 3 | |
| 5.5.0 | 3 / 3 | |
| 5.4.0 | 3 / 3 | |
| 5.3.0 | 3 / 3 | |
| 5.2.0 | 3 / 3 | |
| 4.1.2 | 9 / 4 | |
| 4.0.0 | 9 / 4 | |
| 3.7.6 | 5 / 4 | |
| 3.7.5 | 5 / 4 | |
| 3.7.1 | 5 / 4 | |
| 3.7.0 | 5 / 4 | |
| 3.6.0 | 5 / 4 | |
| 3.5.5 | 5 / 4 | |
| 3.5.4 | 5 / 4 | |
| 3.5.3 | 5 / 4 | |
| 3.5.2 | 5 / 4 | |
| 3.5.0 | 5 / 4 | |
| 3.4.3 | 5 / 4 | |
| 3.4.2 | 5 / 4 | |
| 3.4.1 | 5 / 4 | |
| 3.4.0 | 5 / 4 | |
| 3.3.0 | 5 / 4 | |
| 3.2.0 | 5 / 4 | |
| 3.1.1 | 5 / 4 | |
| 3.0.0 | 5 / 4 | |
| 2.10.0 | 5 / 4 | |
| 2.9.0 | 5 / 4 | |
| 2.8.0 | 5 / 4 | |
| 2.7.0 | 5 / 4 | |
| 2.6.0 | 5 / 4 | |
| 2.5.0 | 5 / 4 | |
| 2.4.0 | 5 / 4 | |
| 2.3.0 | 5 / 4 | |
| 2.2.0 | 5 / 4 | |
| 2.1.1 | 5 / 4 | |
| 2.1.0 | 5 / 4 | |
| 2.0.0 | 5 / 4 |
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
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.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.10.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.