@kb-labs/mind-core
Core contracts, errors, and utilities for KB Labs Mind
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Both new deps are established (globby) or same-org sibling (@kb-labs/mind-contracts); pattern is normal for this monorepo. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals elevate this for this package. | ai |
Versions (showing 51 of 79)
| Version | Deps | Published |
|---|---|---|
| 2.110.0 | 3 / 6 | |
| 2.109.0 | 3 / 6 | |
| 2.107.0 | 3 / 6 | |
| 2.106.0 | 3 / 6 | |
| 2.105.0 | 3 / 6 | |
| 2.104.0 | 3 / 6 | |
| 2.103.0 | 3 / 6 | |
| 2.102.0 | 3 / 6 | |
| 2.101.0 | 3 / 6 | |
| 2.100.0 | 3 / 6 | |
| 2.98.0 | 3 / 6 | |
| 2.96.0 | 3 / 6 | |
| 2.94.0 | 2 / 6 | |
| 2.93.0 | 2 / 6 | |
| 2.89.0 | 2 / 6 | |
| 2.88.0 | 2 / 6 | |
| 2.87.0 | 2 / 6 | |
| 2.82.0 | 2 / 6 | |
| 2.81.0 | 2 / 6 | |
| 2.80.0 | 2 / 6 | |
| 2.79.0 | 2 / 6 | |
| 2.78.0 | 2 / 6 | |
| 2.77.0 | 2 / 6 | |
| 2.75.0 | 2 / 6 | |
| 2.74.0 | 2 / 6 | |
| 2.73.0 | 2 / 6 | |
| 2.72.0 | 2 / 6 | |
| 2.69.0 | 2 / 6 | |
| 2.68.0 | 2 / 6 | |
| 2.67.0 | 2 / 6 | |
| 2.66.0 | 2 / 6 | |
| 2.65.0 | 2 / 6 | |
| 2.64.0 | 2 / 6 | |
| 2.62.0 | 2 / 6 | |
| 2.61.0 | 2 / 6 | |
| 2.60.0 | 2 / 6 | |
| 2.59.0 | 2 / 6 | |
| 2.58.0 | 2 / 6 | |
| 2.57.0 | 2 / 6 | |
| 2.56.0 | 2 / 6 | |
| 2.55.0 | 2 / 6 | |
| 2.54.0 | 2 / 6 | |
| 2.53.0 | 2 / 6 | |
| 2.47.0 | 2 / 6 | |
| 2.46.0 | 2 / 6 | |
| 2.45.0 | 2 / 6 | |
| 2.44.0 | 2 / 6 | |
| 2.43.0 | 2 / 6 | |
| 2.42.0 | 2 / 6 | |
| 2.41.0 | 2 / 6 | |
| 2.40.0 | 2 / 6 |
v2.110.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.109.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.107.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.106.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.105.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.104.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.103.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.102.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.101.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.100.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.96.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: k.baranov.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.65.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.59.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.