@chativa/core
Chativa core — domain interfaces, registries, stores and chat engine (framework-agnostic).
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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/chativa-core.global.js | AI (source-diff): Standard Vite CDN bundle; minification is expected for this artifact across all versions. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @chativa/core is a chat framework core module, not a typosquat of cors; name similarity is coincidental. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 3 / 7 | |
| 0.7.3 | 3 / 7 | |
| 0.7.2 | 3 / 7 | |
| 0.7.1 | 3 / 7 | |
| 0.7.0 | 3 / 7 | |
| 0.6.0 | 3 / 7 | |
| 0.5.0 | 3 / 7 | |
| 0.4.1 | 3 / 6 | |
| 0.4.0 | 3 / 6 | |
| 0.0.1 | 1 / 6 |
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.