@diplodoc/translation
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@diplodoc/sentenizer | AI (dependencies): First-party @diplodoc ecosystem dep; consistent with package purpose across versions. | ai | |
| dependencies | unvetted-dep:@shellscape/i18n-iso-countries | AI (dependencies): Scoped fork of i18n-iso-countries; stable dependency present across prior versions. | ai | |
| provenance | no-provenance | AI (provenance): Established diplodoc-platform package; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:openapi-types | AI (phantom-deps): openapi-types is declared in dependencies in package.json; phantom-dep heuristic misfires here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.7.23 | 22 / 15 | |
| 1.7.21 | 22 / 15 | |
| 1.7.14 | 21 / 16 | |
| 1.7.11 | 21 / 16 | |
| 1.7.10 | 21 / 16 |
v1.7.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.