number-flow
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/lite-B8p0lZvR.js | AI (source-diff): Rollup-minified build output, no malicious behavior; benign for this build-tool-produced dist. | ai | |
| source-diff | obfuscated-file:dist/lite-B614HEDD.js | AI (source-diff): Minified Vite/Rollup dist bundle matching package function; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/continuous-B3Kli2lB.js | AI (source-diff): Minified Vite build output for DOM number animation; not obfuscation, no malicious behavior. | ai | |
| source-diff | obfuscated-file:dist/continuous-DyFEzKlu.js | AI (source-diff): Minified Vite build output, not obfuscation; stable for this build tooling. | ai | |
| source-diff | obfuscated-file:dist/lite-hpz6xQDp.js | AI (source-diff): Minified Rollup dist output, not obfuscation; expected for this build. | ai | |
| source-diff | obfuscated-file:dist/continuous-NkaCOHfo.js | AI (source-diff): Minified vite build output, not obfuscation; benign for this build-tool-produced dist. | ai | |
| source-diff | obfuscated-file:dist/continuous-B1RI4VTB.js | AI (source-diff): Minified Vite build output, not obfuscation; standard dist artifact for this package. | ai | |
| source-diff | obfuscated-file:dist/ssr-B-DD5oSO.js | AI (source-diff): Minified Rollup dist output for number animation; not obfuscation, stable build artifact. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.6.2 | 1 / 12 | |
| 0.6.1 | 1 / 12 | |
| 0.6.0 | 1 / 12 | |
| 0.5.12 | 1 / 12 | |
| 0.5.11 | 1 / 12 | |
| 0.5.10 | 1 / 12 | |
| 0.5.9 | 1 / 12 | |
| 0.5.8 | 1 / 12 | |
| 0.5.7 | 1 / 12 | |
| 0.5.6 | 1 / 12 | |
| 0.5.5 | 1 / 12 | |
| 0.5.4 | 1 / 12 | |
| 0.5.3 | 1 / 12 | |
| 0.5.2 | 1 / 12 | |
| 0.5.1 | 1 / 12 | |
| 0.5.0 | 1 / 12 | |
| 0.4.2 | 1 / 12 | |
| 0.4.1 | 1 / 12 | |
| 0.4.0 | 1 / 12 | |
| 0.3.10 | 1 / 12 | |
| 0.3.9 | 1 / 12 | |
| 0.3.8 | 0 / 11 | |
| 0.3.7 | 0 / 11 | |
| 0.3.6 | 0 / 11 | |
| 0.3.5 | 0 / 11 | |
| 0.3.4 | 0 / 11 | |
| 0.3.3 | 0 / 11 | |
| 0.3.2 | 1 / 11 | |
| 0.3.1 | 1 / 11 | |
| 0.3.0 | 1 / 11 | |
| 0.2.3 | 1 / 7 | |
| 0.2.2 | 1 / 7 | |
| 0.2.1 | 1 / 7 | |
| 0.2.0 | 1 / 7 | |
| 0.1.0 | 1 / 7 |
v0.6.2
1 findingPackage 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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.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.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.