@c8y/api-doc
This package is a blueprint application which allows to show all API documentations of the platform.
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 | publisher-changed | AI (provenance): Transition from named account to GitHub Actions CI publisher is a documented CI/CD migration pattern for this org. | ai | |
| phantom-deps | phantom-dep:@c8y/style | AI (phantom-deps): Same-org sibling package loaded by convention, not direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@angular/cdk | AI (phantom-deps): Framework-scoped Angular package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:monaco-editor | AI (phantom-deps): Referenced in config files for API doc rendering; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:ngx-bootstrap | AI (phantom-deps): Referenced in config files; loaded by convention in Angular app blueprint. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 1023.83.4 | 10 / 3 | |
| 1023.83.3 | 10 / 3 | |
| 1023.83.2 | 10 / 3 | |
| 1023.82.8 | 10 / 3 | |
| 1023.82.4 | 10 / 3 | |
| 1023.82.3 | 10 / 3 | |
| 1023.82.2 | 10 / 3 | |
| 1023.82.1 | 10 / 3 | |
| 1023.82.0 | 10 / 3 | |
| 1023.81.3 | 10 / 3 | |
| 1023.81.2 | 10 / 3 | |
| 1023.80.2 | 10 / 3 | |
| 1023.80.0 | 10 / 3 | |
| 1023.79.1 | 10 / 3 | |
| 1023.78.7 | 10 / 3 | |
| 1023.78.5 | 10 / 3 | |
| 1023.78.4 | 10 / 3 | |
| 1023.78.1 | 10 / 3 | |
| 1023.77.1 | 10 / 3 | |
| 1023.76.0 | 10 / 3 | |
| 1023.75.1 | 10 / 3 | |
| 1023.71.1 | 10 / 3 | |
| 1023.70.0 | 10 / 3 | |
| 1023.68.7 | 10 / 3 | |
| 1023.68.6 | 10 / 3 | |
| 1023.68.3 | 10 / 3 | |
| 1023.68.0 | 10 / 3 | |
| 1023.67.0 | 10 / 3 | |
| 1023.66.4 | 10 / 3 | |
| 1023.66.3 | 10 / 3 | |
| 1023.65.2 | 10 / 3 | |
| 1023.65.1 | 10 / 3 | |
| 1023.65.0 | 10 / 3 | |
| 1023.64.2 | 10 / 3 | |
| 1023.64.1 | 10 / 3 | |
| 1023.63.1 | 10 / 3 | |
| 1023.63.0 | 10 / 3 | |
| 1023.62.2 | 10 / 3 | |
| 1023.61.12 | 10 / 3 | |
| 1023.61.2 | 10 / 3 | |
| 1023.61.0 | 10 / 3 | |
| 1023.59.1 | 10 / 3 | |
| 1023.58.3 | 10 / 3 | |
| 1023.57.0 | 10 / 3 | |
| 1023.55.5 | 10 / 3 | |
| 1023.53.0 | 10 / 3 | |
| 1023.52.0 | 10 / 3 | |
| 1023.50.2 | 10 / 3 | |
| 1023.48.3 | 10 / 3 | |
| 1023.48.2 | 10 / 3 | |
| 1023.48.0 | 10 / 3 |
v1023.83.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.83.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.83.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.82.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.82.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.82.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.82.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.82.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.81.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.81.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.80.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.79.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.78.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.78.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.78.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.75.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.68.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.68.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.68.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.66.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.66.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.65.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.65.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.64.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1023.64.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1023.63.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.63.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.62.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.61.12
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.61.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.61.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.59.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.58.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.57.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.55.5
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.53.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.52.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.50.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.48.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.48.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1023.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.