typeorm-extension
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-standing package with clean history; lack of provenance is common and not a risk indicator here. | ai | |
| dependencies | unvetted-dep:rapiq | AI (dependencies): rapiq is authored by the same maintainer (tada5hi); stable dependency across versions of this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.8.0 | 8 / 21 | |
| 3.7.4 | 8 / 21 | |
| 3.7.3 | 8 / 21 | |
| 3.7.2 | 8 / 20 | |
| 3.7.1 | 9 / 21 | |
| 3.7.0 | 9 / 21 | |
| 3.6.3 | 9 / 21 | |
| 3.6.2 | 9 / 21 | |
| 3.6.1 | 9 / 21 | |
| 3.6.0 | 9 / 21 |
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.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.