← Home

@tinacms/metrics

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

kldavis4scottgallantjeffsee55wicksipediajackpettit-sswrobt-tinakulesy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): TinaCMS migrated to GitHub Actions CI publishing with SLSA attestation; this is a legitimate org-wide automation change. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer consistent with org-level transition to automated publishing pipeline. ai

Versions (showing 3 of 3)

Version Deps Published
2.1.0 0 / 5
2.0.1 0 / 5
2.0.0 1 / 6

v2.1.0

2 findings
HIGH Publisher changed: wicksipedia → GitHub Actions (on 2026-05-12) provenance

This version was published by a different npm account than previous versions on 2026-05-12. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.