← Home

@decaf-ts/for-nano

npm Repository Homepage

decaf-ts persistence adapter for CouchDB via nano

14
Versions
MPL-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

tvenceslauvnogueira91pccostadcardosopdmfcdemersoncarvalho

Keywords

nanocouchdbadapterpersistencedecaftypescriptnosqlreplicationclientdatabase

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@decaf-ts/logging AI (phantom-deps): Same-org scope; likely re-exported transitively rather than directly imported. ai
phantom-deps phantom-dep:@decaf-ts/injectable-decorators AI (phantom-deps): Same-org scope; likely re-exported transitively rather than directly imported. ai
phantom-deps phantom-dep:@decaf-ts/transactional-decorators AI (phantom-deps): Same-org scope; likely re-exported transitively rather than directly imported. ai

Versions (showing 14 of 14)

Version Deps Published
0.2.7 9 / 1
0.2.0 9 / 1
0.1.12 0 / 31
0.1.10 0 / 31
0.1.9 0 / 31
0.1.8 0 / 31
0.1.7 0 / 31
0.1.6 0 / 31
0.1.5 0 / 31
0.1.4 0 / 31
0.1.3 0 / 31
0.1.2 0 / 31
0.1.1 0 / 31
0.1.0 0 / 31

v0.2.7

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.