@timeback/sdk
Timeback SDK for frontend and backend integration
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@timeback/core | AI (dependencies): @timeback/core is a first-party dependency within the same @timeback namespace and publisher; not a suspicious third-party addition. | ai | |
| phantom-deps | phantom-dep:c12 | AI (phantom-deps): c12 is a legitimate unjs config loader; declared as a runtime dep and used in config files. Not being directly imported in source is expected for this usage pattern. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dep likely used for config validation; phantom detection is a false positive for this SDK's architecture. | ai | |
| phantom-deps | phantom-dep:jiti | AI (phantom-deps): jiti is a declared runtime dep used for config file loading; not directly imported in source is expected for this use case. | ai | |
| provenance | no-provenance | AI (provenance): Established SDK package with 75 versions and 97 days history; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.2.5 | 3 / 18 | |
| 0.2.4 | 3 / 18 | |
| 0.2.3 | 3 / 18 | |
| 0.2.2 | 2 / 19 | |
| 0.2.1 | 2 / 19 | |
| 0.2.0 | 2 / 19 | |
| 0.1.14 | 3 / 14 | |
| 0.1.13 | 3 / 13 | |
| 0.1.8 | 3 / 12 | |
| 0.1.7 | 3 / 11 | |
| 0.1.4 | 3 / 8 |
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.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.
v0.2.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.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.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.