@botonic/plugin-hubtype-analytics
Botonic plugin for **Hubtype analytics** integration on the **current** 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Major version jump with pipeline changes explains missing gitHead; known maintainer team.platform. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @botonic/core at matching version — same-org monorepo sibling, not a third-party addition. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the entire @botonic/* ecosystem; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo plugin stub pattern; empty index and missing metadata are consistent across all versions of this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.34.2 | 3 / 0 | |
| 2.34.1 | 3 / 0 | |
| 2.34.0 | 3 / 0 | |
| 2.33.1 | 3 / 0 | |
| 2.33.0 | 3 / 0 | |
| 2.32.0 | 3 / 0 | |
| 2.31.0 | 3 / 0 | |
| 2.30.0 | 3 / 0 | |
| 2.29.0 | 3 / 0 | |
| 2.28.0 | 3 / 0 | |
| 2.27.0 | 2 / 0 | |
| 2.26.0 | 2 / 0 | |
| 0.54.0 | 3 / 1 | |
| 0.53.0 | 3 / 1 | |
| 0.52.0 | 3 / 1 | |
| 0.51.0 | 3 / 1 | |
| 0.50.0 | 3 / 1 | |
| 0.49.0 | 3 / 1 | |
| 0.48.0 | 3 / 1 | |
| 0.47.0 | 3 / 1 | |
| 0.41.0 | 3 / 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
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.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.33.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.
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
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.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.