@synerise/ds-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/i18n/en.json.js | AI (source-diff): Single-line JSON i18n string constant; minified by build tool, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/i18n/es.json.js | AI (source-diff): Single-line JSON i18n string constant; minified by build tool, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/i18n/pl.json.js | AI (source-diff): Single-line JSON i18n string constant; minified by build tool, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/i18n/pt.json.js | AI (source-diff): Single-line JSON i18n string constant; minified by build tool, not obfuscated malware. | ai | |
| provenance | no-provenance | AI (provenance): Established Synerise design system package; no provenance is consistent with all prior versions. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.13.1 | 6 / 5 | |
| 1.13.0 | 6 / 5 | |
| 1.12.3 | 6 / 5 | |
| 1.12.2 | 6 / 5 | |
| 1.12.1 | 6 / 5 | |
| 1.12.0 | 6 / 5 | |
| 1.11.4 | 6 / 5 | |
| 1.11.3 | 6 / 5 | |
| 1.11.2 | 6 / 5 | |
| 1.11.1 | 6 / 5 | |
| 1.11.0 | 6 / 5 | |
| 1.10.2 | 6 / 5 | |
| 1.10.1 | 6 / 5 | |
| 1.10.0 | 6 / 5 | |
| 1.9.1 | 6 / 5 | |
| 1.9.0 | 6 / 5 | |
| 1.8.2 | 6 / 5 | |
| 1.8.1 | 6 / 5 | |
| 1.8.0 | 6 / 5 | |
| 1.7.1 | 6 / 5 | |
| 1.7.0 | 6 / 5 | |
| 1.6.0 | 6 / 5 | |
| 1.5.2 | 6 / 4 | |
| 1.5.1 | 4 / 4 | |
| 1.5.0 | 4 / 4 | |
| 1.4.3 | 4 / 4 | |
| 1.4.2 | 4 / 4 | |
| 1.4.1 | 4 / 4 | |
| 1.4.0 | 4 / 4 | |
| 1.3.1 | 4 / 4 | |
| 1.3.0 | 4 / 4 | |
| 1.2.0 | 4 / 4 | |
| 1.1.0 | 4 / 2 | |
| 1.0.1 | 4 / 2 | |
| 1.0.0 | 4 / 2 |
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.