@backstage-community/plugin-npm
A Backstage plugin that shows meta info and latest versions from a npm registry
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@backstage/theme | AI (phantom-deps): Declared as a runtime dependency in package.json; used via Backstage theming system, not necessarily directly imported. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.23.0 | 12 / 11 | |
| 1.22.0 | 12 / 11 | |
| 1.21.1 | 12 / 11 | |
| 1.21.0 | 12 / 11 | |
| 1.20.0 | 11 / 4 | |
| 1.19.1 | 11 / 4 | |
| 1.19.0 | 11 / 4 | |
| 1.18.1 | 11 / 4 | |
| 1.18.0 | 11 / 4 | |
| 1.17.0 | 11 / 4 | |
| 1.16.0 | 11 / 4 | |
| 1.15.0 | 11 / 4 | |
| 1.14.0 | 11 / 4 | |
| 1.13.0 | 11 / 4 | |
| 1.12.0 | 11 / 4 | |
| 1.11.0 | 11 / 4 | |
| 1.10.1 | 11 / 4 | |
| 1.10.0 | 11 / 7 | |
| 1.9.0 | 11 / 7 | |
| 1.8.0 | 11 / 7 | |
| 1.7.0 | 11 / 7 | |
| 1.6.1 | 11 / 7 | |
| 1.6.0 | 11 / 7 | |
| 1.5.1 | 11 / 7 | |
| 1.5.0 | 11 / 7 | |
| 1.4.0 | 11 / 7 | |
| 1.3.0 | 11 / 7 | |
| 1.2.0 | 11 / 7 | |
| 1.1.0 | 8 / 7 | |
| 1.0.2 | 8 / 9 | |
| 1.0.1 | 8 / 9 | |
| 1.0.0 | 8 / 9 |
v1.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.