@tryghost/mg-hubspot-api
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Org maintainer reshuffle, no code/script changes accompanying it. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with normal team turnover on TryGhost monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Low-traffic internal utility package; dormancy expected, no behavior change in diff. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.4.26 | 4 / 3 | |
| 0.4.25 | 4 / 3 | |
| 0.4.24 | 4 / 3 | |
| 0.4.23 | 4 / 3 | |
| 0.4.22 | 4 / 3 |
v0.4.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.