← Home

@kosdev-code/kos-ddk-models

npm
22
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kosdevmatrica_mark

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Scoped internal SDK package under @kosdev-code org; missing metadata (description, repo, keywords) is typical for internal packages, not indicative of spam or malice. ai
npm-metadata no-description AI (npm-metadata): Internal organizational SDK package; missing description is a hygiene issue, not a security signal for this package. ai
provenance no-provenance AI (provenance): No provenance is common (~88% of npm packages); no other signals suggest tampering for this established package. ai

Versions (showing 22 of 22)

Version Deps Published
3.0.7 3 / 0
3.0.6 3 / 0
3.0.5 3 / 0
3.0.4 3 / 0
3.0.3 3 / 0
3.0.2 3 / 0
3.0.1 3 / 0
3.0.0 3 / 0
2.1.3 3 / 0
2.1.2 3 / 0
2.1.1 3 / 0
2.1.0 3 / 0
2.0.11 3 / 0
2.0.10 3 / 0
2.0.9 3 / 0
2.0.8 3 / 0
2.0.5 3 / 0
2.0.4 3 / 0
2.0.3 3 / 0
2.0.2 3 / 0
2.0.1 3 / 0
2.0.0 3 / 0

v3.0.7

1 finding
INFO No provenance attestation provenance

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

v3.0.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.

v2.0.0

1 finding
INFO No provenance attestation provenance

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