← Home

@cdklabs/tskb

npm Repository Homepage

Using TypeScript as a knowledge base

5
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

amzn-ossaws-cdk-team

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): cdklabs-automation uses projen which pins version at 0.0.0 in package.json; this is a stable pattern across all their packages, not a malware indicator. ai
bogus-package bogus-package AI (bogus-package): Metadata gaps (no repo URL, no keywords, sparse README) are a known pattern for projen-generated CDK Labs packages; not indicative of spam or malware. ai

Versions (showing 5 of 5)

Version Deps Published
0.0.4 0 / 16
0.0.3 0 / 18
0.0.2 0 / 17
0.0.1 0 / 17
0.0.0 0 / 17

v0.0.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

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