@dicebear/core
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/Validator/OptionsValidator.js | AI (source-diff): Pre-compiled AJV validator with inlined JSON Schema; long lines from schema objects, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/Validator/StyleValidator.js | AI (source-diff): Pre-compiled AJV validator with inlined JSON Schema; long lines from schema objects, not obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @dicebear/converter is a same-org monorepo sibling, version-locked; not an external supply chain risk. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @dicebear/core is a legitimate scoped package unrelated to the 'cors' package; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:@types/json-schema | AI (phantom-deps): @types/json-schema is a type-only dependency used at compile time, not imported at runtime; stable false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 10.1.0 | 0 / 5 | |
| 10.0.2 | 0 / 5 | |
| 10.0.1 | 0 / 5 | |
| 10.0.0 | 0 / 5 | |
| 9.4.2 | 1 / 3 | |
| 9.4.1 | 1 / 3 | |
| 8.1.0 | 2 / 4 | |
| 8.0.3 | 2 / 4 | |
| 7.2.0 | 2 / 4 | |
| 7.1.4 | 2 / 4 | |
| 6.3.0 | 2 / 4 | |
| 6.2.0 | 2 / 4 | |
| 6.1.4 | 2 / 4 | |
| 5.6.1 | 1 / 4 | |
| 5.6.0 | 1 / 4 | |
| 5.5.0 | 1 / 4 | |
| 5.4.6 | 1 / 4 | |
| 5.4.5 | 1 / 4 | |
| 5.4.4 | 1 / 4 |
v10.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.