@serenityjs/data
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 | encoded-string-file:dist/index.mjs | AI (source-diff): Same data-table content in ESM build output. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Data-only package with minimal README is expected for this repo. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): Minified bundled data tables (block/item definitions), not true obfuscation. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Long literal data arrays from tsup bundling, not encoded payloads. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Expected from bundling large generated Minecraft data tables. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.8.21 | 0 / 6 | |
| 0.8.20 | 0 / 6 | |
| 0.8.19 | 0 / 6 | |
| 0.8.18 | 0 / 6 | |
| 0.8.17 | 0 / 6 | |
| 0.8.16 | 0 / 6 | |
| 0.8.15 | 0 / 6 | |
| 0.3.4 | 0 / 8 | |
| 0.3.3 | 0 / 8 | |
| 0.3.2 | 0 / 8 | |
| 0.3.1 | 0 / 8 | |
| 0.3.0 | 0 / 8 | |
| 0.2.4 | 0 / 8 | |
| 0.2.3 | 0 / 8 | |
| 0.2.2 | 0 / 8 |
v0.8.19
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 150 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.18
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 150 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.17
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 150 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 150 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 143 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.