← Home

@cossackframework/node-adapter

npm Repository Homepage

Node.js runtime adapter for the Cossack Framework

17
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

tanftw

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): nodemailer is an established, legitimate dependency fitting the package's purpose. ai
provenance missing-githead AI (provenance): Minor publish-environment metadata gap, no provenance regression detected. ai
provenance no-provenance AI (provenance): Small framework package; no other risk signals; provenance absence alone is insufficient to block. ai

Versions (showing 17 of 17)

Version Deps Published
0.7.6 3 / 6
0.7.5 3 / 6
0.7.4 3 / 6
0.7.1 3 / 6
0.7.0 4 / 5
0.6.0 3 / 5
0.5.2 3 / 5
0.5.1 3 / 5
0.5.0 3 / 5
0.4.1 3 / 5
0.4.0 3 / 5
0.3.9 3 / 5
0.1.5 3 / 5
0.1.4 3 / 5
0.1.1 3 / 5
0.1.0 3 / 5
0.0.1 2 / 5

v0.7.6

1 finding
INFO No provenance attestation provenance

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

v0.7.5

1 finding
INFO No provenance attestation provenance

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

v0.7.4

1 finding
INFO No provenance attestation provenance

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

v0.7.1

1 finding
INFO No provenance attestation provenance

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

v0.7.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tanftw.

INFO No provenance attestation provenance

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

v0.6.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tanftw.

INFO No provenance attestation provenance

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