@atomic-ehr/codegen
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): CLI tool; deps likely loaded dynamically at runtime, not via static imports. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): CLI tool; deps likely loaded dynamically at runtime, not via static imports. | ai | |
| phantom-deps | phantom-dep:handlebars | AI (phantom-deps): CLI tool; deps likely loaded dynamically at runtime, not via static imports. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): CLI tool; deps likely loaded dynamically at runtime, not via static imports. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): yargs is a declared runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.0.15 | 6 / 8 | |
| 0.0.14 | 6 / 8 | |
| 0.0.13 | 6 / 8 | |
| 0.0.12 | 6 / 8 | |
| 0.0.11 | 6 / 8 | |
| 0.0.10 | 6 / 8 | |
| 0.0.9 | 7 / 8 | |
| 0.0.8 | 7 / 8 | |
| 0.0.7 | 7 / 8 | |
| 0.0.6 | 7 / 8 | |
| 0.0.5 | 7 / 8 | |
| 0.0.4 | 5 / 7 | |
| 0.0.3 | 5 / 7 | |
| 0.0.2 | 9 / 8 | |
| 0.0.1 | 8 / 8 |
v0.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.