@notion-kit/table-view
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 | large-new-source-files | AI (source-diff): Growth reflects new @notion-kit/* monorepo sub-packages being added; consistent with normal feature expansion. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase driven by bundling additional @notion-kit/* monorepo packages at same version; not injected code. | ai | |
| source-diff | net-exec-file:dist/index.mjs | AI (source-diff): Standard React/TS monorepo bundle; no actual network calls or dynamic code execution present in the file. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-monorepo @notion-kit/* packages pinned to the same version; not third-party additions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo component package; missing description is a consistent pattern across the notion-kit suite. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the notion-kit monorepo; consistent pattern, not a per-version concern. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 11 / 20 | |
| 0.17.0 | 15 / 20 | |
| 0.16.0 | 15 / 20 | |
| 0.15.1 | 15 / 20 | |
| 0.15.0 | 15 / 19 | |
| 0.11.0 | 16 / 11 | |
| 0.10.0 | 16 / 11 | |
| 0.9.1 | 16 / 11 | |
| 0.9.0 | 16 / 11 | |
| 0.8.0 | 12 / 11 | |
| 0.7.0 | 12 / 11 | |
| 0.6.1 | 12 / 11 | |
| 0.6.0 | 12 / 11 |
v1.0.0
2 findingsNewly 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.17.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.