@dawn-ai/core
Shared Dawn app discovery, config loading, route validation, and route type generation primitives.
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 | missing-githead | AI (provenance): Package has SLSA provenance attestation; missing gitHead is a minor CI config difference, not a tampering signal. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @dawn-ai/core; the levenshtein match to 'cors' is a false positive for this namespace. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 8 / 4 | |
| 0.1.8 | 3 / 2 | |
| 0.1.7 | 3 / 2 | |
| 0.1.6 | 3 / 2 | |
| 0.1.5 | 3 / 2 | |
| 0.1.2 | 3 / 2 | |
| 0.1.1 | 3 / 2 | |
| 0.1.0 | 3 / 2 | |
| 0.0.2 | 3 / 2 |
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.5
2 findingsPackage name '@dawn-ai/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.