@intentweave/index
Code-aware retrieval index — SQLite-based index for agents and CI
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/export/vendor/cytoscape.min.js | AI (source-diff): Canonical Cytoscape.js UMD bundle with correct copyright; copied by postbuild script from src/export/vendor. | ai | |
| source-diff | net-exec-file:dist/export/vendor/vendor/cytoscape.min.js | AI (source-diff): Duplicate of cytoscape.min.js due to nested vendor path in build; same canonical library. | ai | |
| source-diff | net-exec-file:dist/export/vendor/dagre.min.js | AI (source-diff): Canonical Dagre graph layout UMD bundle with correct copyright; copied by postbuild script. | ai | |
| source-diff | net-exec-file:dist/export/vendor/vendor/dagre.min.js | AI (source-diff): Duplicate of dagre.min.js due to nested vendor path in build; same canonical library. | ai | |
| provenance | no-provenance | AI (provenance): Young package from a small publisher; no provenance is a process gap, not a security signal here. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): Scoped @intentweave org package; Levenshtein match to 'knex' is coincidental, not a typosquat. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 4 / 5 | |
| 0.13.0 | 4 / 5 | |
| 0.12.0 | 4 / 5 | |
| 0.11.1 | 3 / 5 | |
| 0.11.0 | 3 / 5 | |
| 0.10.0 | 3 / 5 | |
| 0.9.0 | 3 / 5 | |
| 0.8.0 | 3 / 5 | |
| 0.7.0 | 2 / 5 | |
| 0.6.0 | 2 / 5 | |
| 0.5.0 | 2 / 5 | |
| 0.4.0 | 2 / 5 | |
| 0.3.0 | 1 / 5 | |
| 0.1.0 | 1 / 5 |
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
5 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.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.