@botonic/core
Runtime and APIs for Botonic bots: actions, context, messaging, and integration hooks used by the **current** framework line.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:process | AI (phantom-deps): Polyfill used via config/bundler convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-runtime | AI (phantom-deps): Babel plugin loaded by convention, not direct import. | ai | |
| provenance | missing-githead | AI (provenance): Major version restructure changed publish environment; known maintainer team.platform; no malicious indicators. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; provenance not previously required and absence alone is not a risk signal here. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @botonic/core is a long-established framework package, not a typosquat of cors. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.34.2 | 2 / 0 | |
| 2.34.1 | 2 / 0 | |
| 2.34.0 | 2 / 0 | |
| 2.33.1 | 2 / 0 | |
| 2.33.0 | 2 / 0 | |
| 2.32.0 | 2 / 0 | |
| 2.31.0 | 2 / 0 | |
| 2.30.0 | 2 / 0 | |
| 2.29.0 | 2 / 0 | |
| 2.28.0 | 2 / 0 | |
| 2.27.0 | 2 / 0 | |
| 2.26.0 | 2 / 0 | |
| 2.25.0 | 2 / 0 | |
| 2.24.0 | 2 / 0 | |
| 2.23.2 | 2 / 0 | |
| 2.23.1 | 2 / 0 | |
| 2.23.0 | 2 / 0 | |
| 0.53.0 | 6 / 2 | |
| 0.52.1 | 6 / 2 | |
| 0.52.0 | 6 / 2 | |
| 0.51.3 | 6 / 2 | |
| 0.51.2 | 5 / 2 | |
| 0.51.1 | 5 / 2 | |
| 0.51.0 | 5 / 2 | |
| 0.50.1 | 5 / 2 | |
| 0.50.0 | 5 / 2 | |
| 0.49.0 | 5 / 2 | |
| 0.48.1 | 5 / 2 | |
| 0.48.0 | 5 / 2 | |
| 0.47.0 | 5 / 2 | |
| 0.46.1 | 5 / 2 | |
| 0.46.0 | 5 / 2 | |
| 0.45.0 | 5 / 2 | |
| 0.44.0 | 5 / 2 | |
| 0.43.0 | 5 / 2 | |
| 0.42.0 | 5 / 2 | |
| 0.41.0 | 5 / 2 |
v2.34.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: team.platform.
v2.34.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: team.platform.
v2.34.0
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: team.platform.
This version was published by a different npm account (team.platform) than the most recent previously approved version (oraventos) on 2026-07-09, but team.platform is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.33.1
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: team.platform.
This version was published by a different npm account (team.platform) than the most recent previously approved version (oraventos) on 2026-06-29, but team.platform is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.25.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: team.platform.
v2.24.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: team.platform.
v2.23.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: team.platform.
v2.23.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: team.platform.
v2.23.0
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: team.platform.
This version was published by a different npm account (team.platform) than the most recent previously approved version (ahubstre) on 2026-03-23, but team.platform is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (oraventos) than the most recent previously approved version (team.platform) on 2026-07-14, but oraventos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.51.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (oraventos) than the most recent previously approved version (team.platform) on 2026-07-02, but oraventos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.51.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (oraventos) than the most recent previously approved version (team.platform) on 2026-06-29, but oraventos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.46.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ahubstre) than the most recent previously approved version (mrabat) on 2026-03-20, but ahubstre is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (oraventos) than the most recent previously approved version (mrabat) on 2025-11-25, but oraventos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.