@contractspec/lib.ai-agent
AI agent orchestration with MCP and tool support
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 | source-size-tripled | AI (source-diff): Size increase from adding i18n catalogs and telemetry; expected for this feature set. | ai | |
| source-diff | obfuscated-file:dist/node/i18n/keys.js | AI (source-diff): Node variant of Bun-bundled i18n keys; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/node/i18n/messages.js | AI (source-diff): Node variant of Bun-bundled i18n messages; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/node/telemetry/posthog.js | AI (source-diff): Bun-bundled PostHog telemetry wrapper; expected for analytics SDK. | ai | |
| source-diff | obfuscated-file:dist/telemetry/posthog.js | AI (source-diff): Bun-bundled PostHog telemetry wrapper; expected for analytics SDK. | ai | |
| source-diff | net-exec-file:dist/node/telemetry/posthog.js | AI (source-diff): PostHog SDK wrapper; network+exec pattern is inherent to telemetry. | ai | |
| source-diff | net-exec-file:dist/telemetry/posthog.js | AI (source-diff): PostHog SDK wrapper; network+exec pattern is inherent to telemetry. | ai | |
| source-diff | obfuscated-file:dist/i18n/catalogs/en.js | AI (source-diff): Bun-bundled i18n catalog with readable translation strings; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/i18n/catalogs/es.js | AI (source-diff): Bun-bundled i18n catalog (Spanish); not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/i18n/catalogs/fr.js | AI (source-diff): Bun-bundled i18n catalog (French); not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/i18n/catalogs/index.js | AI (source-diff): Bun-bundled i18n index; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/i18n/index.js | AI (source-diff): Bun-bundled i18n entry; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/i18n/keys.js | AI (source-diff): Bun-bundled i18n keys map; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/i18n/messages.d.ts | AI (source-diff): TypeScript declaration with long union type; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/i18n/messages.js | AI (source-diff): Bun-bundled i18n messages; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/node/i18n/catalogs/en.js | AI (source-diff): Node variant of Bun-bundled i18n catalog; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/node/i18n/catalogs/es.js | AI (source-diff): Node variant of Bun-bundled i18n catalog; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/node/i18n/catalogs/fr.js | AI (source-diff): Node variant of Bun-bundled i18n catalog; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/node/i18n/catalogs/index.js | AI (source-diff): Node variant of Bun-bundled i18n index; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/node/i18n/index.js | AI (source-diff): Node variant of Bun-bundled i18n entry; not obfuscated. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google | AI (phantom-deps): Same pattern: provider deps declared for re-export/config use. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): Same pattern: provider deps declared for re-export/config use. | ai | |
| phantom-deps | phantom-dep:@posthog/react | AI (phantom-deps): Same pattern: telemetry dep declared for config use. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/mistral | AI (phantom-deps): Same pattern: provider deps declared for re-export/config use. | ai | |
| phantom-deps | phantom-dep:compare-versions | AI (phantom-deps): Utility dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@posthog/ai | AI (phantom-deps): AI agent library; deps referenced in config/re-exports, not direct imports — stable false positive pattern. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 8.0.17 | 14 / 3 | |
| 8.0.16 | 14 / 3 | |
| 8.0.15 | 14 / 3 | |
| 8.0.14 | 14 / 3 | |
| 8.0.13 | 14 / 3 | |
| 8.0.12 | 14 / 3 | |
| 8.0.11 | 14 / 3 | |
| 8.0.10 | 14 / 3 | |
| 8.0.9 | 14 / 3 | |
| 8.0.8 | 14 / 3 | |
| 8.0.7 | 14 / 3 | |
| 8.0.6 | 14 / 3 | |
| 1.61.0 | 12 / 3 | |
| 1.60.0 | 12 / 3 | |
| 1.59.0 | 12 / 3 | |
| 1.58.0 | 12 / 3 | |
| 1.57.0 | 12 / 4 | |
| 1.56.1 | 11 / 4 | |
| 1.56.0 | 11 / 4 | |
| 1.55.0 | 11 / 4 | |
| 1.54.0 | 11 / 4 | |
| 1.53.0 | 11 / 4 | |
| 1.52.0 | 11 / 4 | |
| 1.51.0 | 11 / 4 | |
| 1.50.0 | 11 / 4 | |
| 1.49.0 | 11 / 4 | |
| 1.48.1 | 11 / 4 | |
| 1.48.0 | 11 / 4 | |
| 1.47.0 | 11 / 4 | |
| 1.46.2 | 11 / 4 | |
| 1.46.1 | 11 / 4 | |
| 1.46.0 | 11 / 4 | |
| 1.45.6 | 11 / 4 | |
| 1.45.5 | 11 / 4 | |
| 1.45.4 | 11 / 4 | |
| 1.45.3 | 11 / 4 | |
| 1.45.2 | 11 / 4 | |
| 1.45.1 | 11 / 4 | |
| 1.45.0 | 11 / 4 | |
| 1.44.1 | 10 / 4 | |
| 1.44.0 | 10 / 4 |
v8.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.15
20 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.
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.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.9
20 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.
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.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.8
20 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.
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.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.