gregorian-calendar-format
format utils for gregorian-calendar
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is in gulpfile.js (dev-only release automation), not in runtime code or install scripts. No consumer risk. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): cp.exec() runs git tag/push in a gulp release task in gulpfile.js. Dev-only, not executed during install or at runtime by consumers. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in server.js is a local dev test server for browser testing, not part of the published runtime API. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4225 days old, predates Sigstore provenance; absence is expected and not a risk signal for this established package. | ai | |
| dependencies | unvetted-dep:gregorian-calendar | AI (dependencies): gregorian-calendar is the core library this package wraps, authored by the same publisher (yiminghe). This is a stable first-party dependency relationship. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 4.1.2 | 2 / 4 | |
| 4.1.1 | 2 / 4 | |
| 4.1.0 | 2 / 4 | |
| 4.0.4 | 2 / 4 | |
| 4.0.3 | 1 / 4 | |
| 4.0.2 | 1 / 4 | |
| 4.0.1 | 1 / 4 | |
| 4.0.0 | 1 / 4 | |
| 3.1.0 | 1 / 4 | |
| 3.0.1 | 1 / 4 | |
| 3.0.0 | 1 / 4 | |
| 2.1.1 | 1 / 4 | |
| 2.1.0 | 1 / 4 | |
| 2.0.2 | 1 / 34 | |
| 2.0.1 | 1 / 34 | |
| 2.0.0 | 1 / 34 | |
| 1.0.4 | 1 / 31 | |
| 1.0.3 | 1 / 31 | |
| 1.0.2 | 0 / 31 | |
| 1.0.1 | 0 / 31 | |
| 1.0.0 | 0 / 30 |
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.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.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.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.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.