@decaf-ts/for-couchdb
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 17 approved packages and consistent org affiliation; dormancy likely reflects project cadence, not takeover. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 96 versions; provenance was never enabled historically. | ai | |
| source-diff | obfuscated-file:dist/for-couchdb.js | AI (source-diff): Standard minified bundle output for a TypeScript CouchDB adapter; no malicious patterns in sample. | ai |
Versions (showing 100 of 113)
| Version | Deps | Published |
|---|---|---|
| 0.14.5 | 0 / 4 | |
| 0.14.4 | 0 / 4 | |
| 0.14.3 | 0 / 4 | |
| 0.14.2 | 0 / 4 | |
| 0.14.1 | 0 / 4 | |
| 0.14.0 | 0 / 4 | |
| 0.13.0 | 0 / 4 | |
| 0.12.0 | 0 / 4 | |
| 0.11.0 | 0 / 4 | |
| 0.10.0 | 0 / 4 | |
| 0.9.0 | 0 / 4 | |
| 0.8.0 | 0 / 4 | |
| 0.7.6 | 0 / 4 | |
| 0.7.5 | 0 / 4 | |
| 0.7.4 | 0 / 4 | |
| 0.7.3 | 0 / 4 | |
| 0.7.2 | 0 / 4 | |
| 0.7.1 | 0 / 4 | |
| 0.7.0 | 0 / 4 | |
| 0.6.3 | 0 / 4 | |
| 0.6.2 | 0 / 4 | |
| 0.6.1 | 0 / 4 | |
| 0.6.0 | 0 / 4 | |
| 0.5.5 | 0 / 4 | |
| 0.5.3 | 0 / 4 | |
| 0.5.2 | 0 / 4 | |
| 0.5.1 | 0 / 4 | |
| 0.5.0 | 0 / 3 | |
| 0.4.40 | 0 / 3 | |
| 0.4.39 | 0 / 3 | |
| 0.4.38 | 0 / 3 | |
| 0.4.37 | 0 / 3 | |
| 0.4.36 | 0 / 3 | |
| 0.4.35 | 0 / 2 | |
| 0.4.34 | 0 / 2 | |
| 0.4.33 | 0 / 2 | |
| 0.4.32 | 0 / 2 | |
| 0.4.31 | 0 / 2 | |
| 0.4.30 | 0 / 2 | |
| 0.4.29 | 0 / 2 | |
| 0.4.28 | 0 / 2 | |
| 0.4.27 | 0 / 2 | |
| 0.4.26 | 0 / 2 | |
| 0.4.25 | 0 / 2 | |
| 0.4.24 | 0 / 2 | |
| 0.4.23 | 0 / 2 | |
| 0.4.22 | 0 / 2 | |
| 0.4.21 | 0 / 2 | |
| 0.4.20 | 0 / 2 | |
| 0.4.19 | 0 / 2 | |
| 0.4.18 | 0 / 2 | |
| 0.4.17 | 0 / 2 | |
| 0.4.16 | 0 / 2 | |
| 0.4.15 | 0 / 2 | |
| 0.4.14 | 0 / 2 | |
| 0.4.13 | 0 / 2 | |
| 0.4.12 | 0 / 2 | |
| 0.4.11 | 0 / 2 | |
| 0.4.10 | 0 / 2 | |
| 0.4.9 | 0 / 2 | |
| 0.4.8 | 0 / 2 | |
| 0.4.6 | 0 / 2 | |
| 0.4.5 | 0 / 2 | |
| 0.4.4 | 0 / 2 | |
| 0.4.3 | 0 / 2 | |
| 0.4.2 | 0 / 2 | |
| 0.4.1 | 0 / 2 | |
| 0.4.0 | 0 / 2 | |
| 0.3.15 | 0 / 26 | |
| 0.3.13 | 0 / 31 | |
| 0.3.11 | 0 / 31 | |
| 0.3.10 | 0 / 31 | |
| 0.3.9 | 0 / 31 | |
| 0.3.8 | 0 / 31 | |
| 0.3.7 | 0 / 31 | |
| 0.3.6 | 0 / 31 | |
| 0.3.5 | 0 / 31 | |
| 0.3.4 | 0 / 31 | |
| 0.3.2 | 0 / 31 | |
| 0.3.1 | 0 / 31 | |
| 0.3.0 | 0 / 31 | |
| 0.2.1 | 0 / 31 | |
| 0.2.0 | 0 / 31 | |
| 0.1.29 | 0 / 37 | |
| 0.1.28 | 0 / 35 | |
| 0.1.27 | 0 / 35 | |
| 0.1.26 | 0 / 35 | |
| 0.1.25 | 0 / 35 | |
| 0.1.24 | 0 / 35 | |
| 0.1.23 | 0 / 35 | |
| 0.1.22 | 0 / 35 | |
| 0.1.21 | 0 / 35 | |
| 0.1.20 | 0 / 35 | |
| 0.1.18 | 0 / 35 | |
| 0.1.17 | 6 / 35 | |
| 0.1.16 | 6 / 35 | |
| 0.1.15 | 6 / 35 | |
| 0.1.14 | 6 / 35 | |
| 0.1.13 | 6 / 35 | |
| 0.1.12 | 6 / 35 |
v0.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.29
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.28
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.27
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.26
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.25
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.24
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.23
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.22
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.21
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.20
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.18
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.17
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.16
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.15
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.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.