@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 13 of 113)
| Version | Deps | Published |
|---|---|---|
| 0.1.11 | 6 / 35 | |
| 0.1.10 | 6 / 35 | |
| 0.1.9 | 6 / 35 | |
| 0.1.8 | 6 / 35 | |
| 0.1.7 | 6 / 35 | |
| 0.1.6 | 6 / 35 | |
| 0.1.5 | 6 / 35 | |
| 0.1.4 | 6 / 35 | |
| 0.1.3 | 0 / 35 | |
| 0.1.2 | 0 / 35 | |
| 0.1.1 | 0 / 35 | |
| 0.1.0 | 0 / 35 | |
| 0.0.2 | 0 / 37 |
v0.1.11
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.10
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.9
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.6
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.5
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.
v0.1.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.
v0.1.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.
v0.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.
v0.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.
v0.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.