@eventcatalog/sdk
3
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.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 |
v2.1.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.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.
v2.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.