@credo-ts/action-menu
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package is published via GitHub Actions CI/CD with SLSA attestation from the openwallet-foundation org; publisher=GitHub Actions is expected. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is a declared runtime dependency; phantom-dep fires on config-file references, stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 5 / 2 | |
| 0.6.3 | 5 / 2 | |
| 0.6.2 | 5 / 2 | |
| 0.6.1 | 5 / 2 | |
| 0.6.0 | 5 / 2 | |
| 0.5.19 | 4 / 3 | |
| 0.5.18 | 4 / 3 | |
| 0.5.17 | 4 / 3 | |
| 0.5.16 | 4 / 3 | |
| 0.5.15 | 4 / 3 | |
| 0.5.14 | 4 / 3 |
v0.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.