@rightcapital/date-helpers
Format dates with date-fns.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation; gitHead absence is a cosmetic gap, not a supply chain risk for this org's CI pipeline. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI/CD publishing for a monorepo with 681 versions; rapid successive publishes are expected and attested via SLSA. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.1.30 | 2 / 2 | |
| 3.1.29 | 2 / 2 | |
| 3.1.28 | 2 / 2 | |
| 3.1.27 | 2 / 2 | |
| 3.1.26 | 2 / 2 | |
| 3.1.25 | 2 / 2 | |
| 3.1.24 | 2 / 2 | |
| 3.1.23 | 2 / 2 | |
| 3.1.22 | 2 / 2 |
v3.1.30
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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.