@netacea/f5
Netacea F5 CDN integration
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:f5-nodejs | AI (dependencies): f5-nodejs is the expected F5 iRules LX SDK dependency for this F5 CDN integration package; stable across versions. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @netacea package; Levenshtein match against 'pg' is a false positive for this CDN integration. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @netacea package; Levenshtein match against 'qs' is a false positive for this CDN integration. | ai | |
| phantom-deps | phantom-dep:f5-nodejs | AI (phantom-deps): f5-nodejs is an F5 platform runtime dep used via config; not directly imported in source but legitimately declared. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 5.8.4 | 2 / 24 | |
| 5.8.3 | 2 / 24 | |
| 5.8.2 | 2 / 24 | |
| 5.8.1 | 2 / 24 | |
| 5.8.0 | 2 / 24 | |
| 5.7.0 | 2 / 24 | |
| 5.6.5 | 2 / 24 | |
| 5.6.0 | 2 / 24 | |
| 5.5.2 | 2 / 24 | |
| 5.5.1 | 2 / 24 | |
| 5.4.1 | 2 / 24 | |
| 5.4.0 | 2 / 24 | |
| 5.3.7 | 2 / 24 | |
| 5.3.6 | 2 / 24 | |
| 5.3.5 | 2 / 24 | |
| 5.3.2 | 2 / 24 | |
| 5.2.3 | 2 / 24 | |
| 5.2.0 | 2 / 24 | |
| 4.3.147 | 2 / 24 | |
| 4.3.138 | 2 / 24 | |
| 4.3.136 | 2 / 24 | |
| 4.3.133 | 2 / 24 |
v5.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.147
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.