@timeback/qti
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @timeback/qti is a scoped package for QTI (e-learning standard); levenshtein match to 'qs' is a false positive with no brand impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @timeback/qti is a scoped package for QTI (e-learning standard); levenshtein match to 'joi' is a false positive with no brand impersonation intent. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 2 / 5 | |
| 0.3.0 | 2 / 5 | |
| 0.2.2 | 2 / 5 | |
| 0.2.1 | 1 / 6 | |
| 0.2.0 | 1 / 6 | |
| 0.1.0 | 0 / 6 |
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.