@github/relative-time-element
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | slsa-provenance | AI (provenance): Official @github org package published via verified CI/CD with Sigstore attestation; stable pattern. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is expected for @github org packages moving to automated CI/CD publishing. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy followed by org-level CI/CD migration is consistent with legitimate maintenance resumption for this @github package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 0 / 12 | |
| 5.1.0 | 0 / 12 | |
| 5.0.0 | 0 / 12 | |
| 4.5.1 | 0 / 12 |
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.