@notion-kit/tags-input
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance across all @notion-kit/* packages; consistent publishing pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped monorepo package; missing description is consistent across the @notion-kit/* family. | ai | |
| phantom-deps | phantom-dep:@hookform/resolvers | AI (phantom-deps): Listed as a runtime dependency; phantom detection likely misses indirect usage in bundled output. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.17.0 | 5 / 10 | |
| 0.16.0 | 5 / 10 | |
| 0.15.1 | 5 / 10 | |
| 0.15.0 | 5 / 10 | |
| 0.11.0 | 6 / 9 | |
| 0.10.0 | 6 / 9 | |
| 0.9.0 | 6 / 9 | |
| 0.8.0 | 5 / 9 | |
| 0.7.0 | 5 / 9 | |
| 0.6.1 | 5 / 9 | |
| 0.6.0 | 5 / 9 | |
| 0.5.0 | 5 / 9 | |
| 0.4.0 | 5 / 9 |
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 finding[Accepted risk] 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage 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.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.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.