← Home

@talismn/connection-meta

npm Repository Homepage
41
Versions
GPL-3.0-or-later
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

0xkheopsalectalisman

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package predating widespread provenance adoption; no provenance across all versions. ai
bogus-package bogus-package AI (bogus-package): Established monorepo package; sparse README/metadata is consistent across all versions. ai
npm-metadata no-description AI (npm-metadata): Intentional for this monorepo package; stable across versions. ai

Versions (showing 41 of 41)

Version Deps Published
0.3.1 2 / 3
0.3.0 2 / 3
0.2.39 2 / 3
0.2.38 2 / 3
0.2.37 2 / 3
0.2.36 2 / 3
0.2.35 2 / 2
0.2.34 2 / 2
0.2.33 2 / 7
0.2.32 2 / 7
0.2.31 2 / 7
0.2.30 2 / 7
0.2.29 2 / 7
0.2.28 2 / 7
0.2.27 2 / 7
0.2.26 2 / 7
0.2.25 2 / 7
0.2.23 2 / 7
0.2.22 2 / 7
0.2.21 2 / 7
0.2.20 2 / 7
0.2.19 2 / 7
0.2.18 2 / 7
0.2.17 2 / 7
0.2.16 2 / 7
0.2.15 2 / 7
0.2.14 2 / 7
0.2.13 2 / 7
0.2.12 2 / 7
0.2.11 2 / 7
0.2.10 2 / 7
0.2.9 2 / 7
0.2.8 2 / 7
0.2.7 2 / 7
0.2.6 2 / 7
0.2.5 2 / 7
0.2.4 2 / 7
0.2.3 2 / 7
0.2.2 2 / 7
0.2.1 2 / 7
0.2.0 2 / 7

v0.3.1

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.2.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.2.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.2.3

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.2.2

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.2.1

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.

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