@absolutejs/rag
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of the @absolutejs org ecosystem; sparse metadata is a style choice, not spam. | ai | |
| source-diff | obfuscated-file:dist/quality/quality.js | AI (source-diff): Bun-bundled output with readable source; long lines from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/index.d.ts | AI (source-diff): Long TypeScript declaration file with readable export names; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/client/ui.js | AI (source-diff): Bun-bundled output with readable source; long lines from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/index.js | AI (source-diff): Bun-bundled output with readable source; long lines from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/presentation/ui.js | AI (source-diff): Bun-bundled output with readable source; long lines from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/quality/quality.d.ts | AI (source-diff): Long TypeScript declaration file with readable type names; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Bun-bundled output with readable source; long lines from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/ai/rag/index.d.ts | AI (source-diff): Long lines are TypeScript declaration exports, not obfuscated code. Stable pattern for this bundled .d.ts package. | ai | |
| source-diff | obfuscated-file:dist/src/ai/rag/quality.d.ts | AI (source-diff): Long lines are TypeScript type union declarations. False positive for bundled .d.ts files. | ai | |
| source-diff | obfuscated-file:dist/src/ai/rag/types.d.ts | AI (source-diff): Long lines are TypeScript re-export type declarations. False positive for bundled .d.ts files. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped RAG framework package; edit-distance match to 'pg' is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:@absolutejs/linked-providers | AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for scoped monorepo packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.0.18 | 2 / 16 | |
| 0.0.16 | 2 / 16 | |
| 0.0.15 | 2 / 16 | |
| 0.0.12 | 2 / 16 | |
| 0.0.11 | 2 / 16 | |
| 0.0.10 | 2 / 16 | |
| 0.0.9 | 2 / 16 | |
| 0.0.8 | 2 / 16 | |
| 0.0.7 | 2 / 16 | |
| 0.0.6 | 2 / 16 | |
| 0.0.5 | 2 / 16 | |
| 0.0.4 | 2 / 16 | |
| 0.0.3 | 2 / 16 | |
| 0.0.2 | 2 / 8 | |
| 0.0.1 | 3 / 7 |
v0.0.18
9 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alexkahndev.
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.
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.
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.
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.
v0.0.16
9 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alexkahndev.
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.
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.
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.
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.
v0.0.15
9 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alexkahndev.
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.
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.
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.
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.
v0.0.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alexkahndev.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
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.
v0.0.5
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.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.