@worknice/whiteboard
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher change is within the same org; viniworknice confirmed as known maintainer on prior approved versions. | ai | |
| npm-metadata | url-dep:@worknice/commit-analyzer | AI (npm-metadata): Dev-only build tool from the same org (WorkniceHR); no runtime impact. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is a stable pattern across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped package with 367 versions; metadata signals are false positives for this internal component library. | ai | |
| phantom-deps | phantom-dep:@rsbuild/plugin-mdx | AI (phantom-deps): Used in build config files, not directly imported in source — expected pattern for build plugins. | ai |
Versions (showing 50 of 150)
| Version | Deps | Published |
|---|---|---|
| 0.11.0 | 14 / 29 | |
| 0.10.19 | 14 / 29 | |
| 0.10.18 | 14 / 29 | |
| 0.10.17 | 14 / 29 | |
| 0.10.16 | 14 / 29 | |
| 0.10.15 | 14 / 29 | |
| 0.10.14 | 14 / 29 | |
| 0.10.13 | 14 / 29 | |
| 0.10.12 | 14 / 29 | |
| 0.10.11 | 14 / 29 | |
| 0.10.10 | 14 / 29 | |
| 0.10.9 | 14 / 29 | |
| 0.10.8 | 14 / 29 | |
| 0.10.7 | 14 / 29 | |
| 0.10.6 | 14 / 29 | |
| 0.10.5 | 14 / 29 | |
| 0.10.4 | 14 / 29 | |
| 0.10.3 | 14 / 29 | |
| 0.10.2 | 14 / 29 | |
| 0.10.1 | 14 / 29 | |
| 0.10.0 | 14 / 29 | |
| 0.9.1 | 14 / 29 | |
| 0.9.0 | 14 / 29 | |
| 0.8.3 | 14 / 29 | |
| 0.8.2 | 14 / 29 | |
| 0.8.1 | 14 / 29 | |
| 0.8.0 | 14 / 29 | |
| 0.7.0 | 14 / 26 | |
| 0.6.0 | 13 / 27 | |
| 0.5.0 | 13 / 27 | |
| 0.4.6 | 13 / 27 | |
| 0.4.5 | 13 / 27 | |
| 0.4.4 | 13 / 27 | |
| 0.4.3 | 13 / 27 | |
| 0.4.2 | 13 / 27 | |
| 0.4.1 | 13 / 27 | |
| 0.4.0 | 13 / 27 | |
| 0.3.3 | 13 / 27 | |
| 0.3.2 | 13 / 27 | |
| 0.3.1 | 13 / 27 | |
| 0.3.0 | 13 / 27 | |
| 0.2.6 | 13 / 27 | |
| 0.2.5 | 13 / 27 | |
| 0.2.4 | 13 / 27 | |
| 0.2.3 | 13 / 27 | |
| 0.2.2 | 13 / 27 | |
| 0.2.1 | 13 / 27 | |
| 0.2.0 | 13 / 27 | |
| 0.1.1 | 13 / 27 | |
| 0.0.3 | 13 / 24 |
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.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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
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.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
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.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
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.