@valtimo/dossier-management
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard implicit dependency for Angular/TypeScript libraries; stable pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package; missing metadata is typical for internal libraries, not spam. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 12.39.0 | 1 / 0 | |
| 12.38.0 | 1 / 0 | |
| 12.37.0 | 1 / 0 | |
| 12.36.0 | 1 / 0 | |
| 12.35.0 | 1 / 0 | |
| 12.34.0 | 1 / 0 | |
| 12.33.1 | 1 / 0 | |
| 12.33.0 | 1 / 0 | |
| 12.32.0 | 1 / 0 | |
| 12.31.0 | 1 / 0 | |
| 12.30.0 | 1 / 0 | |
| 12.29.0 | 1 / 0 | |
| 12.28.1 | 1 / 0 | |
| 12.28.0 | 1 / 0 | |
| 12.27.0 | 1 / 0 | |
| 12.26.0 | 1 / 0 | |
| 12.25.0 | 1 / 0 | |
| 12.24.0 | 1 / 0 | |
| 12.23.1 | 1 / 0 | |
| 12.23.0 | 1 / 0 | |
| 12.22.0 | 1 / 0 | |
| 12.21.1 | 1 / 0 | |
| 12.21.0 | 1 / 0 | |
| 12.20.1 | 1 / 0 | |
| 12.20.0 | 1 / 0 | |
| 12.19.0 | 1 / 0 | |
| 12.18.0 | 1 / 0 | |
| 12.17.1 | 1 / 0 | |
| 12.17.0 | 1 / 0 | |
| 12.16.1 | 1 / 0 | |
| 12.16.0 | 1 / 0 | |
| 12.15.1 | 1 / 0 | |
| 12.15.0 | 1 / 0 | |
| 12.14.1 | 1 / 0 | |
| 12.14.0 | 1 / 0 | |
| 12.12.0 | 1 / 0 | |
| 12.6.1 | 1 / 0 | |
| 12.6.0 | 1 / 0 | |
| 12.5.1 | 1 / 0 | |
| 12.5.0 | 1 / 0 | |
| 12.4.2 | 1 / 0 | |
| 12.4.1 | 1 / 0 | |
| 12.4.0 | 1 / 0 | |
| 12.3.1 | 1 / 0 | |
| 12.3.0 | 1 / 0 | |
| 12.2.1 | 1 / 0 | |
| 12.2.0 | 1 / 0 | |
| 12.1.3 | 1 / 0 | |
| 12.0.1 | 1 / 0 | |
| 12.0.0 | 1 / 0 |
v12.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.