@botonic/react
Build Chatbots using React
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer team.platform; no behavioral change. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher has strong track record (218 approved, 0 rejected); legitimate transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same trusted-publisher transition, not indicative of compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with 339 versions; resumption of publishing after dormancy is plausible for an active OSS project. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-known, widely-used Markdown parser; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package; lack of provenance is consistent across its 337-version history and not a risk signal here. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 0.54.0 | 13 / 18 | |
| 0.53.0 | 13 / 18 | |
| 0.52.0 | 13 / 18 | |
| 0.51.0 | 13 / 18 | |
| 0.50.0 | 13 / 18 | |
| 0.49.0 | 13 / 18 | |
| 0.48.3 | 13 / 18 | |
| 0.48.2 | 13 / 18 | |
| 0.48.1 | 13 / 18 | |
| 0.48.0 | 13 / 18 | |
| 0.47.0 | 13 / 18 | |
| 0.46.0 | 13 / 18 | |
| 0.45.0 | 13 / 18 | |
| 0.44.1 | 13 / 18 | |
| 0.44.0 | 13 / 18 | |
| 0.43.1 | 13 / 19 | |
| 0.43.0 | 13 / 19 | |
| 0.42.1 | 13 / 19 | |
| 0.42.0 | 13 / 19 | |
| 0.41.0 | 13 / 19 | |
| 0.40.1 | 13 / 19 | |
| 0.40.0 | 13 / 19 | |
| 0.39.0 | 13 / 19 | |
| 0.38.0 | 13 / 19 | |
| 0.37.1 | 13 / 19 | |
| 0.37.0 | 13 / 19 | |
| 0.36.5 | 13 / 19 | |
| 0.36.4 | 13 / 19 | |
| 0.36.3 | 13 / 19 | |
| 0.36.2 | 13 / 19 | |
| 0.36.1 | 13 / 19 | |
| 0.36.0 | 13 / 19 | |
| 0.35.0 | 13 / 19 | |
| 0.34.1 | 13 / 17 | |
| 0.34.0 | 13 / 17 | |
| 0.33.1 | 13 / 17 | |
| 0.33.0 | 13 / 17 | |
| 0.32.0 | 13 / 17 | |
| 0.31.1 | 13 / 17 | |
| 0.31.0 | 13 / 17 | |
| 0.30.8 | 13 / 15 | |
| 0.30.7 | 13 / 15 | |
| 0.30.6 | 13 / 15 | |
| 0.30.5 | 13 / 15 | |
| 0.30.4 | 13 / 15 | |
| 0.30.3 | 13 / 15 | |
| 0.30.2 | 13 / 14 | |
| 0.30.1 | 13 / 14 | |
| 0.30.0 | 13 / 14 | |
| 0.29.0 | 17 / 15 | |
| 0.28.2 | 17 / 15 |
v0.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.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.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 (mrabat) than the most recent previously approved version (oraventos) on 2026-01-15, but mrabat 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.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.
v0.40.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 (oraventos) on 2025-10-21, 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.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.5
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 (oraventos) on 2025-07-14, 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.36.3
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 (oraventos) on 2025-06-30, 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.36.2
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-06-26, 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.34.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.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-04-01, 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.33.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 (mrabat) on 2025-03-24, 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.33.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 (mrabat) than the most recent previously approved version (oraventos) on 2025-03-04, but mrabat 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.32.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 (mrabat) than the most recent previously approved version (oraventos) on 2025-02-18, but mrabat 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.31.1
2 findingsThis version was published by a different npm account than previous versions on 2025-02-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.3
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 (mrabat) than the most recent previously approved version (oraventos) on 2024-10-29, but mrabat 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.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.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 (mrabat) than the most recent previously approved version (oraventos) on 2024-08-16, but mrabat 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.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.