@credo-ts/askar
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Listed as runtime dep in package.json; used via build output in this monorepo package. | ai | |
| phantom-deps | phantom-dep:tsyringe | AI (phantom-deps): Listed as runtime dep in package.json; used via build output in this monorepo package. | ai | |
| phantom-deps | phantom-dep:class-validator | AI (phantom-deps): Listed as runtime dep in package.json; used via build output in this monorepo package. | ai | |
| phantom-deps | phantom-dep:class-transformer | AI (phantom-deps): Listed as runtime dep in package.json; used via build output in this monorepo package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 5 / 7 | |
| 0.6.3 | 5 / 7 | |
| 0.6.1 | 5 / 7 | |
| 0.6.0 | 5 / 7 | |
| 0.5.19 | 8 / 9 | |
| 0.5.18 | 8 / 9 | |
| 0.5.17 | 6 / 9 | |
| 0.5.16 | 6 / 9 | |
| 0.5.15 | 6 / 9 | |
| 0.5.14 | 6 / 9 |
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.