noon
no ordinary object notation
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:js/noon.js | AI (source-diff): File is koffee-compiled JavaScript (header says '// koffee 0.43.0'). Long lines are static string literals (CLI help text), not obfuscation. Stable for this package. | ai | |
| source-diff | obfuscated-file:js/parse.js | AI (source-diff): File is koffee-compiled JavaScript (header says '// koffee 0.43.0'). Readable, structured code with normal patterns. Not obfuscated. | ai | |
| source-diff | obfuscated-file:js/stringify.js | AI (source-diff): File is koffee-compiled JavaScript (header says '// koffee 0.56.0'). Readable, structured code with normal patterns. Not obfuscated. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is due to adding pre-compiled koffee/JS output files to the package distribution. Legitimate build artifact addition. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): The require() call uses a static string literal argument for CLI help text, not a dynamic variable. False positive for this package. | ai |
Versions (showing 51 of 114)
| Version | Deps | Published |
|---|---|---|
| 3.5.0 | 2 / 3 | |
| 3.4.0 | 2 / 3 | |
| 3.1.0 | 2 / 3 | |
| 3.0.3 | 2 / 3 | |
| 3.0.0 | 4 / 3 | |
| 2.15.0 | 5 / 3 | |
| 2.14.1 | 5 / 3 | |
| 2.14.0 | 5 / 6 | |
| 2.13.0 | 5 / 6 | |
| 2.12.3 | 5 / 6 | |
| 2.12.2 | 5 / 6 | |
| 2.12.1 | 5 / 3 | |
| 2.11.0 | 5 / 3 | |
| 2.10.0 | 5 / 3 | |
| 2.9.0 | 5 / 3 | |
| 2.8.0 | 5 / 3 | |
| 2.7.0 | 5 / 3 | |
| 2.6.0 | 5 / 3 | |
| 2.5.0 | 5 / 3 | |
| 2.4.0 | 5 / 3 | |
| 2.3.0 | 6 / 3 | |
| 2.0.2 | 6 / 3 | |
| 2.0.0 | 6 / 3 | |
| 1.5.0 | 7 / 2 | |
| 1.4.0 | 7 / 2 | |
| 1.3.1 | 7 / 2 | |
| 1.3.0 | 7 / 2 | |
| 1.2.0 | 7 / 2 | |
| 1.1.2 | 5 / 2 | |
| 1.1.1 | 5 / 2 | |
| 1.1.0 | 6 / 2 | |
| 1.0.14 | 6 / 2 | |
| 1.0.13 | 6 / 2 | |
| 1.0.12 | 7 / 2 | |
| 1.0.11 | 7 / 2 | |
| 1.0.9 | 7 / 2 | |
| 1.0.8 | 7 / 2 | |
| 1.0.6 | 7 / 2 | |
| 1.0.5 | 7 / 2 | |
| 1.0.4 | 7 / 2 | |
| 1.0.3 | 7 / 2 | |
| 1.0.2 | 7 / 2 | |
| 1.0.1 | 7 / 2 | |
| 0.9.17 | 7 / 2 | |
| 0.9.16 | 7 / 2 | |
| 0.9.15 | 7 / 2 | |
| 0.9.14 | 7 / 2 | |
| 0.9.13 | 7 / 2 | |
| 0.9.12 | 7 / 2 | |
| 0.9.11 | 7 / 2 | |
| 0.9.10 | 7 / 2 |
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.