@serenityjs/nbt
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/index.mjs | AI (source-diff): tsup bundle output, not true obfuscation; no malicious behavior present. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Growth from bundled dist file, not injected payload. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Active monorepo with 885 versions; rapid publishes are normal for coordinated releases. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package; sparse README/metadata is typical for internal sub-packages. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Scoped @serenityjs package in established monorepo; not a typosquat of nuxt. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @serenityjs package in established monorepo; not a typosquat of got. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped @serenityjs package in established monorepo; not a typosquat of next. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.8.21 | 1 / 6 | |
| 0.8.20 | 1 / 6 | |
| 0.8.19 | 1 / 6 | |
| 0.8.18 | 1 / 6 | |
| 0.8.17 | 1 / 6 | |
| 0.8.16 | 1 / 6 | |
| 0.8.15 | 1 / 6 | |
| 0.8.14 | 1 / 6 | |
| 0.8.13 | 1 / 6 | |
| 0.8.12 | 1 / 6 | |
| 0.8.11 | 1 / 6 | |
| 0.8.10 | 1 / 6 | |
| 0.8.9 | 1 / 6 | |
| 0.8.8 | 1 / 6 | |
| 0.8.7 | 1 / 6 | |
| 0.8.6 | 1 / 6 | |
| 0.8.5 | 1 / 6 | |
| 0.8.4 | 1 / 6 | |
| 0.8.3 | 1 / 6 | |
| 0.8.2 | 1 / 6 | |
| 0.8.1 | 1 / 6 | |
| 0.8.0 | 1 / 6 | |
| 0.7.8 | 1 / 6 | |
| 0.7.7 | 1 / 6 | |
| 0.7.6 | 1 / 6 | |
| 0.7.5 | 1 / 6 | |
| 0.7.4 | 1 / 6 | |
| 0.7.3 | 1 / 6 | |
| 0.7.2 | 1 / 6 | |
| 0.7.1 | 1 / 6 | |
| 0.7.0 | 1 / 6 | |
| 0.6.4 | 1 / 6 | |
| 0.6.3 | 1 / 6 | |
| 0.6.2 | 1 / 6 | |
| 0.6.1 | 1 / 6 | |
| 0.6.0 | 1 / 6 | |
| 0.5.2 | 1 / 8 | |
| 0.5.1 | 1 / 8 | |
| 0.5.0 | 1 / 8 | |
| 0.4.4 | 1 / 8 | |
| 0.4.3 | 1 / 8 | |
| 0.4.2 | 1 / 8 | |
| 0.4.1 | 1 / 8 | |
| 0.4.0 | 1 / 8 | |
| 0.3.6 | 1 / 8 | |
| 0.3.5 | 1 / 8 | |
| 0.3.4 | 1 / 8 | |
| 0.3.3 | 1 / 8 | |
| 0.3.2 | 1 / 8 | |
| 0.3.1 | 1 / 8 | |
| 0.3.0 | 1 / 8 | |
| 0.2.4 | 1 / 8 | |
| 0.2.3 | 1 / 8 | |
| 0.2.2 | 1 / 8 |
v0.8.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.