@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 — the axios compromise (March 2026) relied on exactly this gap.
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): 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 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.29.0 | 3 / 0 | |
| 2.28.0 | 3 / 0 | |
| 2.27.0 | 2 / 0 | |
| 2.26.0 | 2 / 0 | |
| 0.49.0 | 3 / 1 | |
| 0.48.0 | 3 / 1 | |
| 0.47.0 | 3 / 1 | |
| 0.41.0 | 3 / 2 |
v2.29.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: team.platform.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.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: team.platform.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.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-05-28, 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.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.