← Home

@eventcatalog/sdk

npm Repository Homepage
100
Versions
—
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

boyney123

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:proper-lockfile AI (phantom-deps): tsup-bundled SDK; deps used at build/runtime but not directly imported in analyzed source. ai
phantom-deps phantom-dep:commander AI (phantom-deps): Used by new CLI bin entry; bundled via tsup. ai
phantom-deps phantom-dep:gray-matter AI (phantom-deps): tsup-bundled SDK; deps used at build/runtime but not directly imported in analyzed source. ai
phantom-deps phantom-dep:glob AI (phantom-deps): tsup-bundled SDK; deps used at build/runtime but not directly imported in analyzed source. ai
phantom-deps phantom-dep:semver AI (phantom-deps): tsup-bundled SDK; deps used at build/runtime but not directly imported in analyzed source. ai
phantom-deps phantom-dep:slugify AI (phantom-deps): tsup-bundled SDK; deps used at build/runtime but not directly imported in analyzed source. ai
phantom-deps phantom-dep:fs-extra AI (phantom-deps): tsup-bundled SDK; deps used at build/runtime but not directly imported in analyzed source. ai
phantom-deps phantom-dep:@changesets/cli AI (phantom-deps): @changesets/cli is a release tooling dep used in scripts, not imported in source; stable false positive for this package. ai
provenance publisher-changed AI (provenance): Package migrated to GitHub Actions publishing with SLSA attestation; this is the expected publisher going forward. ai

Versions (showing 100 of 103)

Version Deps Published
2.26.3 6 / 8
2.26.2 6 / 8
2.26.1 6 / 8
2.26.0 6 / 8
2.25.0 6 / 8
2.24.2 6 / 8
2.24.1 6 / 8
2.24.0 6 / 8
2.23.1 6 / 8
2.23.0 6 / 8
2.22.0 6 / 8
2.21.2 6 / 8
2.21.1 6 / 8
2.21.0 6 / 8
2.20.0 6 / 8
2.19.0 6 / 8
2.18.4 6 / 8
2.18.3 6 / 8
2.18.2 6 / 8
2.18.1 6 / 8
2.18.0 6 / 8
2.17.4 6 / 8
2.17.3 6 / 8
2.17.2 6 / 8
2.17.1 6 / 8
2.17.0 6 / 8
2.16.0 6 / 8
2.15.1 6 / 8
2.15.0 6 / 8
2.14.3 6 / 8
2.14.2 6 / 8
2.14.1 7 / 8
2.14.0 7 / 8
2.13.2 7 / 8
2.13.1 7 / 8
2.13.0 8 / 8
2.12.1 8 / 8
2.12.0 8 / 8
2.11.0 7 / 8
2.10.0 7 / 8
2.9.11 7 / 8
2.9.10 7 / 8
2.9.9 7 / 8
2.9.8 7 / 8
2.9.7 7 / 8
2.9.6 7 / 8
2.9.5 7 / 8
2.9.2 7 / 8
2.9.1 7 / 8
2.9.0 7 / 8
2.8.4 7 / 8
2.8.3 7 / 8
2.8.2 7 / 8
2.8.1 7 / 8
2.8.0 7 / 8
2.7.6 7 / 8
2.7.5 7 / 8
2.7.4 7 / 8
2.7.3 7 / 8
2.7.2 7 / 8
2.7.1 7 / 8
2.7.0 7 / 8
2.6.9 7 / 8
2.6.8 7 / 8
2.6.7 7 / 8
2.6.6 7 / 8
2.6.5 7 / 8
2.6.4 7 / 8
2.6.3 7 / 8
2.6.2 7 / 8
2.6.1 7 / 8
2.6.0 7 / 8
2.5.5 7 / 8
2.5.4 7 / 8
2.5.3 7 / 8
2.5.2 7 / 8
2.5.1 7 / 8
2.5.0 7 / 8
2.4.0 7 / 8
2.3.7 7 / 8
2.3.6 7 / 8
2.3.5 7 / 8
2.3.4 7 / 8
2.3.3 7 / 8
2.3.2 7 / 8
2.3.1 7 / 8
2.3.0 7 / 8
2.2.10 7 / 8
2.2.9 7 / 8
2.2.8 7 / 8
2.2.7 7 / 8
2.2.6 7 / 8
2.2.5 7 / 8
2.2.4 7 / 8
2.2.3 7 / 8
2.2.2 7 / 8
2.2.1 7 / 8
2.2.0 7 / 8
2.1.2 7 / 8
2.1.1 7 / 8
Showing 100 of 103 Next page →

v2.26.3

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.

v2.26.2

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.

v2.26.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.

v2.26.0

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.

v2.25.0

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.

v2.3.6

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.

v2.3.5

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.

v2.3.4

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.

v2.3.3

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.

v2.3.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.

v2.3.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.

v2.3.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.

v2.2.10

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.

v2.2.9

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.

v2.2.8

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.

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

v2.2.6

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.

v2.2.5

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.

v2.2.4

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.

v2.2.3

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.

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

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

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

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

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