@forinda/kickjs-devtools-kit
Types, RPC envelopes, runtime sampler, and memory analyzer used by KickJS DevTools and any plugin that integrates with it
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:dist/memory-analyzer-DEWEtvB_.mjs | AI (source-diff): Standard tsdown minified ESM bundle output; readable code, no obfuscation or malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/memory-analyzer-BI1a2I-X.mjs | AI (source-diff): Minified ESM build artifact from tsdown; content is readable Node.js perf/memory monitoring code, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/memory-analyzer-BJVPtSqM.mjs | AI (source-diff): Minified bundler output (tsdown); license header present, content is standard Node.js perf monitoring code. | ai | |
| source-diff | obfuscated-file:dist/memory-analyzer-BrX2DMUp.mjs | AI (source-diff): Minified ESM build artifact from tsdown; content is performance/memory monitoring logic with no malicious patterns. | ai | |
| provenance | publisher-changed | AI (provenance): Package now published via GitHub Actions CI with SLSA attestation; this is the expected automated publishing pattern. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 5.4.1 | 0 / 4 | |
| 5.4.0 | 0 / 4 | |
| 5.3.2 | 0 / 4 | |
| 5.3.1 | 0 / 4 | |
| 5.3.0 | 0 / 4 | |
| 5.2.0 | 0 / 4 | |
| 5.1.0 | 0 / 4 | |
| 5.0.2 | 0 / 4 | |
| 5.0.1 | 0 / 4 | |
| 5.0.0 | 0 / 4 | |
| 4.2.0 | 0 / 4 | |
| 4.1.0 | 0 / 4 | |
| 4.0.0 | 0 / 4 |
v5.4.1
2 findingsNewly 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.
v5.4.0
2 findingsNewly 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.
v5.3.2
2 findingsNewly 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.
v5.3.1
3 findingsThis version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.
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.
v5.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.